Facility management system and facility management method

Abstract

To provide a facility management system and a facility management method that easily integrate a database to facilitate management jobs.SOLUTION: A facility management system in which a plurality of business operator servers (a facility member server 1b, a maintenance business operator server 1c, and a facility owner server 1d) corresponding to a plurality of business operators which perform maintenance and management on facilities 5 and a shared server 1a that those business operator servers share are connected through a network N is characterized in that the plurality of business operator servers (the facility member server 1b, the maintenance business operator server 1c, and the facility owner server 1d) receive work records related with the maintenance and management of facility members, maintenance operators and the facility owner, and the shared server 1a displays a list of work that the respective business operators have performed based upon predetermined information included in the work records.SELECTED DRAWING: Figure 1

Description

[Technical Field]

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

[0002] Building facilities include many facilities that need to be managed, such as water supply and drainage systems, electrical systems, and fire protection systems.

[0003] For example, commercial air conditioners and commercial freezers / refrigerators are required to undergo simple inspections at least once every three months and regular inspections at least once a year. To support such inspection work, an application such as that described in Patent Document 1 below is used. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2016-212544 Summary of the Invention [Problem to be solved by the invention]

[0005] In addition to the regular inspections mentioned above, facility management also involves tasks such as installation, repair, inventory, and disposal of equipment. These management tasks are carried out by multiple business operators, including facility owners, facility managers, and maintenance companies, all of whom work together in cooperation with one another.

[0006] However, various problems have arisen due to the lack of information sharing among these multiple businesses.

[0007] For example, when a facility owner takes an inventory of equipment for asset management, they may also need to check the condition of the equipment, and so inspection work may be performed at the same time. Meanwhile, facility managers also perform inspection work based on a pre-established schedule, such as once every three months. However, because information sharing between businesses is not progressing, it is not possible for businesses to know when each other's inspection work was performed. As a result, both businesses sometimes end up performing overlapping inspection work.

[0008] In another example, a maintenance contractor must report the inspection work they performed on equipment to a facility manager, who must then approve it. However, because each business has its own database, they do not share a common management number or other information that uniquely identifies the equipment. Therefore, the facility manager must manually verify whether the equipment reported by the maintenance contractor matches the equipment that was actually inspected.

[0009] One way to solve the above problem would be to integrate the databases managed by each operator. However, each operator manages their equipment using a unique identifier, and unifying these identifiers still requires manual work, so it is not easy to integrate the databases in a reliable manner.

[0010] In view of the above, an object of the present invention is to provide a facility management system and a facility management method that can easily integrate databases and facilitate management operations. [Means for solving the problem]

[0011] The above object of the present invention can be achieved by the following means: Note that the parentheses indicate reference symbols of embodiments to be described later, but the present invention is not limited to these.

[0012] The facility management system according to the invention of claim 1 comprises: In a facility management system in which reading devices (e.g., access point 2 and handy terminal 3 shown in FIG. 1) used by multiple business operators who maintain and manage the same facility (e.g., facility 5 shown in FIG. 1), multiple business operators' servers (e.g., facility staff server 1b, maintenance company server 1c, and facility owner server 1d shown in FIG. 1) corresponding to the multiple business operators, and a shared server (e.g., shared server 1a shown in FIG. 1) shared by the multiple business operators' servers are connected via a network (e.g., network N shown in FIG. 1), An identification tag (e.g., active RFID 5a or barcode 5b shown in FIG. 1) holding an identifier (e.g., device IDtbl_Sb, device IDtbl_Mb, device IDtbl_Ob shown in FIGS. 3(b) to 3(c)) for identifying the equipment (e.g., equipment 5 shown in FIG. 1) is attached to the equipment (e.g., equipment 5 shown in FIG. 1), The reading device (for example, the access point 2 and the handy terminal 3 shown in FIG. 1) reads the identifiers (for example, the device IDtbl_Sb, the device IDtbl_Mb, and the device IDtbl_Ob shown in FIGS. 3(b) to 3(c)) from the identifiers (for example, the active RFID 5a and the barcode 5b shown in FIG. 1) when the plurality of businesses perform work on the facilities. the law of nature, The business server (for example, the facility staff server 1b, the maintenance company server 1c, and the facility owner server 1d shown in FIG. 1) The reading device (for example, the access point 2 or the handy terminal 3 shown in FIG. 1) reads A work record (for example, the facility staff table TBL_S, maintenance contractor table TBL_M, and facility owner table TBL_O shown in FIGS. 3(b) to (c)) including the identifier (for example, the equipment ID tbl_Sb, equipment ID tbl_Mb, and equipment ID tbl_Ob shown in FIGS. 3(b) to (c)) is stored, and the work record further includes the content of the work (for example, the work tbl_Sd, work tbl_Md, and work tbl_Od shown in FIGS. 3(b) to (c)) and the date on which the work was performed (for example, the date tbl_Sc, date tbl_Mc, and date tbl_Oc shown in FIGS. 3(b) to (c)), The shared server (for example, the shared server 1a shown in FIG. 1) is characterized in that it acquires at least the identifier (for example, the equipment IDtbl_Sb, equipment IDtbl_Mb, equipment IDtbl_Ob shown in FIGS. 3(b) to (c)), the content of the work (for example, the work tbl_Sd, work tbl_Mb, work tbl_Od shown in FIGS. 3(b) to (c)), and the date on which the work was performed (for example, the date tbl_Sc, date tbl_Mc, date tbl_Oc shown in FIGS. 3(b) to (c)) from two or more of the multiple business operator servers (for example, the facility staff server 1b, maintenance company server 1c, and facility owner server 1d shown in FIG. 1), combines them, and displays them (for example, the work list screen 6 shown in FIG. 4) on a specified terminal screen (for example, the terminal screen P shown in FIG. 4).

[0013] The facility management system according to the invention of claim 2 is as follows: The business entity server (for example, the facility staff server 1b, the maintenance company server 1c, or the facility owner server 1d shown in FIG. 1) further receives from the reading device (for example, the access point 2 or the handy terminal 3 shown in FIG. 1) the location (for example, the store tbl_Sa, the store tbl_Ma, or the store tbl_Oa shown in FIGS. 3(b) to 3(c)) of the reading device (for example, the access point 2 or the handy terminal 3 shown in FIG. 1) when the reading device (for example, the access point 2 or the handy terminal 3 shown in FIG. 1) reads the identifier (for example, the device IDtbl_Sb, the device IDtbl_Mb, or the device IDtbl_Ob shown in FIGS. 3(b) to 3(c)), The shared server (for example, the shared server 1a shown in FIG. 1) further acquires the locations (for example, the stores tbl_Sa, tbl_Ma, and tbl_Oa shown in FIGS. 3(b) to (c)), combines them, and displays them (for example, the work list screen 6 shown in FIG. 4) on the specified terminal screen (for example, the terminal screen P shown in FIG. 4).

[0014] The facility management system according to the invention of claim 3 comprises: The business operator server (for example, the facility staff server 1b, maintenance company server 1c, facility owner server 1d shown in Figure 1) is further characterized in that it receives from the reading device (for example, the access point 2, handheld terminal 3 shown in Figure 1) the date (date tbl_Sc, date tbl_Mc, date tbl_Oc) when the reading device (for example, the access point 2, handheld terminal 3 shown in Figure 1) read the identifier (for example, the device IDtbl_Sb, device IDtbl_Mb, device IDtbl_Ob shown in Figures 3(b) to (c)) as a timestamp, and stores this as the date when the work was performed (for example, the date tbl_Sc, date tbl_Mc, date tbl_Oc shown in Figures 3(b) to (c)).

[0015] The facility management system according to the invention of claim 4 comprises: The identification tag (for example, the barcode 5b shown in FIG. 1) is characterized by being at least one of a one-dimensional barcode and a two-dimensional barcode.

[0016] The facility management system according to the invention of claim 5 comprises: The above (for example, the active RFID 5a shown in FIG. 1) is characterized by being an active RFID tag.

[0017] The facility management system according to the invention of claim 6 comprises: The shared server (for example, the shared server 1a shown in FIG. 1) is further characterized in that, when the number of times that the work of a specified content is performed reaches a specified number within a specified period in the work records (for example, the facility staff table TBL_S, the maintenance company table TBL_M, and the facility owner table TBL_O shown in FIGS. 3(b) to (c)) stored in the multiple business server (for example, the facility staff server 1b, the maintenance company server 1c, and the facility owner server 1d shown in FIG. 1), an inspection work is suggested (for example, display 6h shown in FIG. 4).

[0018] The facility management system according to the invention of claim 7 comprises: In a facility management method, reading devices (e.g., access point 2 and handy terminal 3 shown in FIG. 1) used by a plurality of business operators who maintain and manage the same facility (e.g., facility 5 shown in FIG. 1), a plurality of business operators' servers (e.g., facility staff server 1b, maintenance company server 1c, and facility owner server 1d shown in FIG. 1) corresponding to the plurality of business operators, and a shared server (e.g., shared server 1a shown in FIG. 1) shared by the plurality of business operators' servers (e.g., facility staff server 1b, maintenance company server 1c, and facility owner server 1d shown in FIG. 1) are connected via a network (e.g., network N shown in FIG. 1), When the plurality of businesses perform work on the facility (for example, the facility 5 shown in FIG. 1), the reading device (for example, the access point 2 and the handy terminal 3 shown in FIG. 1) but 3(b) to 3(c)), and reads an identification tag (for example, active RFID 5a, barcode 5b shown in FIG. 1) that holds an identifier (for example, device IDtbl_Sb, device IDtbl_Mb, device IDtbl_Ob shown in FIG. 3(b) to 3(c)) that identifies the equipment (for example, equipment 5 shown in FIG. 1). take Steps and The business server (for example, the facility staff server 1b, the maintenance company server 1c, or the facility owner server 1d shown in FIG. 1) reads the information read by the reading device (for example, the access point 2 or the handy terminal 3 shown in FIG. 1). storing a work record (for example, facility staff table TBL_S, maintenance contractor table TBL_M, facility owner table TBL_O shown in FIGS. 3(b) to (c)) including the identifier (for example, device ID tbl_Sb, device ID tbl_Mb, device ID tbl_Ob shown in FIGS. 3(b) to (c)), and further including the content of the work (for example, work tbl_Sd, work tbl_Md, work tbl_Od shown in FIGS. 3(b) to (c)) and the date on which the work was performed (for example, date tbl_Sc, date tbl_Mc, date tbl_Oc shown in FIGS. 3(b) to (c)); The shared server (for example, the shared server 1a shown in FIG. 1)The method is characterized by including a step of acquiring at least the identifier (e.g., equipment IDtbl_Sb, equipment IDtbl_Mb, equipment IDtbl_Ob shown in Figures 3(b) to (c)), the content of the work (e.g., work tbl_Sd, work tbl_Md, work tbl_Od shown in Figures 3(b) to (c)), and the date on which the work was performed (e.g., date tbl_Sc, date tbl_Mc, date tbl_Oc shown in Figures 3(b) to (c)) from two or more of the multiple business operator servers (e.g., facility staff server 1b, maintenance company server 1c, facility owner server 1d shown in Figure 1), combining them, and displaying them (e.g., work list screen 6 shown in Figure 4) on a specified terminal screen (e.g., terminal screen P shown in Figure 4). [Effects of the Invention]

[0019] Next, the effects of the present invention will be described with reference to the drawings. Note that the reference symbols in parentheses are those of the embodiments described below, but the present invention is not limited to these.

[0020] According to the inventions of claims 1 and 7, a shared server (for example, shared server 1a shown in FIG. 1) can acquire at least identifiers (for example, equipment ID tbl_Sb, equipment ID tbl_Mb, equipment ID tbl_Ob shown in FIGS. 3(b) to (c)), work contents (for example, work tbl_Sd, work tbl_Mb, work tbl_Od shown in FIGS. 3(b) to (c)), and dates (for example, date tbl_Sc, date tbl_Mc, date tbl_Oc shown in FIGS. 3(b) to (c)) for work records related to work performed by each business operator (for example, facility staff server 1b, maintenance company server 1c, facility owner server 1d shown in FIG. 1), combine them, and output (for example, work list screen 6 shown in FIG. 4). Furthermore, since equipment (for example, equipment 5 shown in Figure 1) can be identified by a common identifier (for example, device IDtbl_Ka shown in Figure 3(a)), it is possible to easily and centrally grasp at least the outline of the work performed by multiple businesses.

[0021] Therefore, according to the present invention, it is possible to provide a facility management system that easily integrates databases and makes management work easier.

[0022] According to the invention of claim 2, it is possible to know the location (for example, store tbl_Sa, store tbl_Ma, store tbl_Oa shown in Figures 3(b) to (c)) of the reading device (for example, access point 2, handheld terminal 3 shown in Figure 1), thereby making it possible to know more details about the work that has been performed.

[0023] According to the invention of claim 3, the date (for example, date tbl_Sc, date tbl_Mc, date tbl_Oc shown in Figures 3(b) to (c)) when the identifier (for example, device IDtbl_Sb, device IDtbl_Mb, device IDtbl_Ob shown in Figures 3(b) to (c)) is read is received as a timestamp, so a highly reliable date can be obtained.

[0024] According to the invention of claim 4, one identification tag (for example, barcode 5b shown in FIG. 1) can be reliably and individually read by a reading device (for example, handy terminal 3 shown in FIG. 1).

[0025] According to the invention of claim 5, a reading device (for example, the access point 2 or the handy terminal 3 shown in FIG. 1) can read multiple identification tags (for example, the active RFID 5a shown in FIG. 1) at once.

[0026] According to the invention of claim 6, when it is determined that the condition of the equipment (for example, equipment 5 shown in Figure 1) may be deteriorating based on the number of times repair work has been performed, for example, when repair work has been performed multiple times, it is possible to suggest inspection work (for example, display 6h shown in Figure 4). [Brief explanation of the drawings]

[0027] [Figure 1] 1 is a block diagram showing an embodiment of a facility management system according to the present invention; [Figure 2] 2A is a block diagram showing a data processing unit of the shared server shown in FIG. 1 according to the embodiment, and FIG. 2B is a block diagram showing a data processing unit of the facility staff server shown in FIG. 1 according to the embodiment. [Figure 3] 2(a) to 2(d) are diagrams showing data tables stored in the servers of FIG. 1. [Figure 4] FIG. 4 is a diagram showing a task list screen in which the data in the data tables shown in FIGS. 3(a) to (d) is combined and displayed. DETAILED DESCRIPTION OF THE INVENTION

[0028] An embodiment of a facility management system according to the present invention will now be described in detail with reference to the drawings. In the following description, when referring to directions such as up, down, left, and right, they refer to the directions as viewed from the front of the illustration.

[0029] <Overall system description> As shown in Figure 1, the facility management system comprises an access point 2, a handheld terminal 3, a shared server 1a, a facility staff server 1b, a maintenance company server 1c, and a facility owner server 1d, all connected via a network N. The access point 2 and the handheld terminal 3 are used to read active RFID tags 5a and barcodes 5b attached to facilities 5 located in a facility 4, a disposal site 40, or a repair storage facility 41.

[0030] <Explanation of active RFID and barcode> As shown in Fig. 1, the active RFID 5a and the barcode 5b are attached to the equipment 5 and hold a device ID (see Fig. 3(a)) that uniquely identifies the equipment 5. The device ID (see Fig. 3(a)) of the active RFID 5a and the barcode 5b can be read by the access point 2 and the handy terminal 3, which will be described later.

[0031] The active RFID 5a can transmit the information it holds over a wide range of several tens to several hundreds of meters, making it suitable for receiving the device IDs (see FIG. 3(a)) of multiple pieces of equipment 5 all at once. On the other hand, the barcode 5b does not unintentionally receive the RFID signal of an adjacent piece of equipment 5, making it suitable for reading the device ID (see FIG. 3(a)) of a single piece of equipment 5.

[0032] Therefore, in this embodiment, when work is performed on multiple pieces of equipment 5, such as inspection or inventory, the active RFID 5a is received by the access point 2, while when work is performed on a single piece of equipment 5, such as repair or disposal, the barcode 5b is read by the handy terminal 3. However, the present invention is not limited to this.

[0033] <Access point description> As shown in Figure 1, the access point 2 receives the device ID (see Figure 3(a)) held by the active RFID 5a attached to the facility 5 via an RFID signal at the RFID signal receiving unit 22, adds the location of the access point 2 and the date of reception at the control unit 20, and transmits it to either the facility staff server 1b, maintenance company server 1c, or facility owner server 1d shown in Figure 1 at the communication unit 21.

[0034] The server to which the data is to be sent is set in advance in the access point 2 using an IP address or the like.

[0035] The location of the access point 2 is determined by obtaining latitude and longitude using a GPS (not shown) built into the access point 2, and transmitting this to the relevant server as the location of the access point 2. The server that receives this converts the latitude and longitude to the store (location within the store) by, for example, preparing a conversion table in advance for converting between latitude and longitude and the store (location within the store).

[0036] The received date is also obtained by obtaining a timestamp from a timestamp authority (not shown) on network N, and this is sent to the relevant server as the date the device ID (see Figure 3(a)) was received. This allows for the transmission of a highly reliable date.

[0037] <Handy terminal explanation> As shown in Figure 1, the handheld terminal 3 reads the device ID (see Figure 3(a)) held by the barcode 5b attached to the equipment 5 using the 2D code reading unit 32, and the control unit 30 adds the location of the handheld terminal 3 and the date of reading, and transmits it via the communication unit 31 to either the facility staff server 1b, the maintenance company server 1c, or the facility owner server 1d shown in Figure 1.

[0038] As with access point 2, the server to which the data is sent is set in advance using an IP address, etc. As with access point 2, the location of handheld terminal 3 and the date it was read can be obtained using a GPS function or a time stamp station.

[0039] <Shared server description> As shown in Figure 1, the shared server 1a is composed of a control unit 10a consisting of a CPU etc., a communication unit 11a that can connect to the network N via communication means such as wireless LAN, wired LAN, dial-up etc., and a shared database 12a.

[0040] The shared database 12a stores a device information table tbl_K (see FIG. 3(a)) which is a master table for the equipment 5.

[0041] The control unit 10a will be specifically described below with reference to FIG. 2(a).

[0042] <Explanation of the control section> 2(a), the control unit 10a is composed of a determination unit 10a1, an initial registration unit 10a2, a work list display unit 10a3, and an inspection suggestion unit 10a4. Each component will be described in detail below.

[0043] <Description of the judgment section> The judgment unit 10a1 exchanges information between each functional block based on the state held by the judgment unit 10a1 or the state held by each functional block, and also exchanges information with the access point 2 and the handy terminal 3 via the communication unit 11a, and also exchanges information with the shared database 12a.

[0044] <Explanation of the initial registration part> The initial registration unit 10a2 creates a device information table tbl_K (see FIG. 3(a)) that serves as a master table for the equipment 5.

[0045] Specifically, when new equipment 5 is installed, the initial registration unit 10a2 receives from the handheld terminal 3 a device ID read by the handheld terminal 3 from the barcode 5b of the equipment 5, along with the location of the handheld terminal 3 and the date the data was read. The initial registration unit 10a2 then stores the received device ID in the device ID tbl_Ka of the equipment information table tbl_K (see FIG. 3(a)), the received date in the installation date tbl_Kc of the equipment information table tbl_K (see FIG. 3(a)), and stores the received location (latitude and longitude) converted into a store or within the store in the store tbl_Kd and installation location tbl_Ke of the equipment information table tbl_K (see FIG. 3(a)).

[0046] Note that input into each field other than those mentioned above in the equipment information table tbl_K (see FIG. 3(a)), i.e., name tbl_Kb indicating the name of the equipment 5, model tbl_Kf indicating the model of the equipment 5, serial number tbl_Kg indicating the serial number of the equipment 5, and other fields tbl_Kh, may be done manually or automatically by another application (not shown). Furthermore, the work content and other data may be set in the access point 2 or the handy terminal 3 and received from the access point 2 or the handy terminal 3.

[0047] By doing so, the initial registration unit 10a2 creates the device information table tbl_K (see FIG. 3(a)).

[0048] The device information table tbl_K (see FIG. 3(a)) can be used to check the installation location of the equipment 5 during inventory work. That is, for example, when inventory work is performed at store A, the active RFID 5a of the equipment 5 can be read using access point 2 at store A and checked against the device ID tbl_Ka in the device information table tbl_K for store tbl_Kd "store A." In this case, if the active RFID 5a of the equipment 5 is read using access point 2 at store A, but the device ID tbl_Ka "ID01A" cannot be read at store A, it is possible to take into account that the equipment has been moved to another store and read the active RFID 5a of the equipment 5 using access point 2 at the other store. This makes it easy to perform inventory work.

[0049] <Explanation of the work list display area> When a facility staff member, maintenance company, or facility owner instructs the shared server 1a to display a work list using a terminal such as a PC or smartphone (not shown), the work list display unit 10a3 acquires specified information from the work records stored in the facility staff server 1b, maintenance company server 1c, and facility owner server 1d shown in Figure 1, generates the work list screen 6 shown in Figure 4, and displays it on the terminal screen (see Figure 4) of the facility staff member, maintenance company, or facility owner's terminal.

[0050] Specifically, the information stored in the store tbl_Sa, equipment ID tbl_Sb, date tbl_Sc, and task tbl_Sd of the facility staff table tbl_S (see FIG. 3(b)) stored in the facility staff server 1b is acquired.

[0051] Similarly, the information stored in the store tbl_Ma, device ID tbl_Mb, date tbl_Mc, and work tbl_Md fields of the maintenance contractor table tbl_M (see FIG. 3(c)) stored in the maintenance contractor server 1c is acquired.

[0052] Similarly, the information stored in the store tbl_Oa, device ID tbl_Ob, date tbl_Oc, and work tbl_Od fields of the facility owner table tbl_O (see FIG. 3(d)) stored in the facility owner server 1d is also acquired.

[0053] The acquired information is then displayed in chronological order in the corresponding columns on the work list screen 6. That is, information acquired from stores tbl_Sa in the facility staff table tbl_S (see FIG. 3(b)), stores tbl_Ma in the maintenance contractor table tbl_M (see FIG. 3(c)), and stores tbl_Oa in the facility owner table tbl_O (see FIG. 3(d)) is displayed in the store column 6a.

[0054] Furthermore, information obtained from the equipment ID tbl_Sb in the facility staff table tbl_S (see FIG. 3(b)), the equipment ID tbl_Mb in the maintenance contractor table tbl_M (see FIG. 3(c)), and the equipment ID tbl_Ob in the facility owner table tbl_O (see FIG. 3(d)) is displayed in the equipment ID column 6b. The equipment ID may be converted into the name of the machine or the like in the equipment information table TBL_K (see FIG. 3(a)) and displayed.

[0055] In addition, information obtained from the date tbl_Sc of the facility staff table tbl_S (see Figure 3(b)), the date tbl_Mc of the maintenance company table tbl_M (see Figure 3(c)), and the date tbl_Oc of the facility owner table tbl_O (see Figure 3(d)) is displayed in the date column 6c1, 6d1, or 6e1 depending on the server from which the information was obtained (facility staff server 1b, maintenance company server 1c, facility owner server 1d).

[0056] In addition, information obtained from the work tbl_Sd of the facility staff table tbl_S (see Figure 3(b)), the work tbl_Md of the maintenance contractor table tbl_M (see Figure 3(c)), and the work tbl_Od of the facility owner table tbl_O (see Figure 3(d)) is displayed in the date column 6c2, 6d2, or 6e2 depending on the server from which the information was obtained (facility staff server 1b, maintenance contractor server 1c, facility owner server 1d).

[0057] Furthermore, based on the fact that record R3 (i.e., the maintenance company's work record) shown in Figure 4 indicates that equipment 5 at store B, whose equipment ID is ID03B, has been discarded, the work list display unit 10a3 additionally displays, in the area where the inventory work at store B is displayed based on the facility owner's work record, that ID03B has been discarded, as in display 6g.

[0058] By doing so, the work list display unit 10a3 generates the work list screen 6 shown in FIG. <Explanation of the inspection proposal section>

[0059] The inspection suggestion unit 10a4 displays a display 6h on the work list screen 6 and suggests an inspection work when a work of a specified content (repair in this embodiment) is performed a specified number of times (twice in this embodiment) within a specified period (one year in this embodiment).

[0060] Specifically, based on the fact that repair work or requests for repair work have occurred twice within one year (see records R4 and R6 in Figure 4), the inspection suggestion unit 10a4 displays a display 6h on the work list screen 6 proposing inspection work for all equipment 5 at store A on December 20, 2022.

[0061] Although not shown, if repair work or a request for repair work has been performed a specified number of times within a specified period for the same equipment, a suggestion for inspection work may be displayed only for that same equipment in the area where the work content is displayed based on the work records of the facility staff, as in display 6h.

[0062] <Facility staff server, maintenance company server, facility owner server> Next, we will explain the facility staff server 1b, maintenance company server 1c, and facility owner server 1d, which store the information required for the shared server 1a to display the work list screen 6. Since these three servers have similar configurations, we will first explain the facility staff server 1b, and then explain the differences between the maintenance company server 1c and the facility owner server 1d and the facility staff server 1b.

[0063] <Facility staff server> As shown in Figure 1, the facility staff server 1b is composed of a control unit 10b consisting of a CPU etc., a communication unit 11b that can connect to the network N via communication means such as wireless LAN, wired LAN, dial-up, etc., and a database 12b.

[0064] The database 12b stores a facility staff table tbl_S shown in FIG. 3(b).

[0065] The control unit 10b of the facility staff server 1b will be specifically described below with reference to FIG. 2(b).

[0066] <Explanation of the control section> 2(b), the control unit 10b is made up of a determination unit 10b1 and a work record receiving unit 10b2. Each component will be described in detail below.

[0067] <Description of the judgment section> The judgment unit 10b1 exchanges information between each functional block based on the state held by the judgment unit 10b1 or the state held by each functional block, and exchanges information with the access point 2 and the handy terminal 3 via the communication unit 11b, and also exchanges information with the database 12b.

[0068] <Work Record Reception Department> The work record receiving unit 10b2 creates the facility staff table tbl_S (see FIG. 3(b)). That is, when a facility staff member performs work on equipment 5, the work record receiving unit 10b2 receives the device ID read by the access point 2 or handy terminal 3, along with the location of the access point 2 or handy terminal 3 and the date the ID was read. The work record receiving unit 10b2 then converts the received location (latitude and longitude) into a store and stores it in the store tbl_Sa field of the facility staff table tbl_S (see FIG. 3(b)) while storing the received device ID in the device ID tbl_Sb field and the date the ID was received in the date tbl_Sc field.

[0069] In addition, when a facility staff member uses the access point 2 to obtain the device IDs of all the equipment 5 installed in the facility 4 as shown in record R1 in FIG. 3(b), the work record receiving unit 10b2 may store "all" as in record R1 in the facility staff table tbl_S. For example, when the store TBL_Kd in the equipment information table TBL_K (see FIG. 3(a)) receives all the device IDs of the equipment 5 at a predetermined location (e.g., "Store A") within a predetermined time, it may store "all." Alternatively, because the active RFID 5a transmits the information it holds as an RFID signal over a wide range of tens to hundreds of meters, it may be set to "all" based on the fact that the information is received from the access point 2.

[0070] In addition, the work content of the facility staff (e.g., "inspection") is entered into each field other than those mentioned above in the facility staff table tbl_S (see Figure 3(b)), i.e., the work content tbl_Sd. In addition, other data that is not made public to the shared server 1a (e.g., the name of the inspector) can be entered into other fields tbl_Se. Furthermore, if it is determined as a result of the inspection work that repairs are required for the equipment 5, it is possible to add "ID04B Repair Request" or the like, as in record R1 of the facility staff table tbl_S.

[0071] These inputs and additions may be done manually or automatically by another application (not shown). Furthermore, the work contents and other data may be set in the access point 2 or the handy terminal 3 and received from the access point 2 or the handy terminal 3.

[0072] <Maintenance company server description> The maintenance contractor server 1c has almost the same configuration as the facility staff server 1b, except that the database 12c stores a maintenance contractor table tbl_M instead of a facility staff table tbl_S.

[0073] Record R2-1 in the maintenance contractor table tbl_M indicates that the maintenance contractor has brought equipment 5 with a device ID of ID03B into the repair storage facility 41 shown in Fig. 1. For example, the maintenance contractor uses the handheld terminal 3 at the repair storage facility 41 to read the barcode 5b of the equipment 5 brought into the repair storage facility 41, thereby creating a work record such as record R2-1.

[0074] Furthermore, record R2-2 in the maintenance contractor table tbl_M indicates that the maintenance contractor has brought equipment 5 with a device ID of ID03B from the repair storage 41 shown in Fig. 1 (see record R2-1) to the disposal site 40. For example, the maintenance contractor uses the handheld terminal 3 at the disposal site 40 to read the barcode 5b of the equipment 5 brought to the disposal site 40, thereby creating a work record such as record R2-2.

[0075] In this way, if the position of the handy terminal 3 when the handy terminal 3 reads the barcode 5b is stored in the work record, it is possible to know in more detail the work that has been performed.

[0076] Furthermore, such a work record of the transportation of the equipment 5 to the disposal site 40 shown in FIG. 1 is particularly effective when the equipment 5 is a refrigeration and air conditioning equipment that uses a substance other than fluorocarbons as a refrigerant. Refrigeration and air conditioning equipment can be broadly divided into those that use fluorocarbons as a refrigerant and those that use other substances, such as natural gas. Disposal methods for the former are stipulated by the Fluorocarbons Control Act. On the other hand, there are no regulations for the latter, and therefore refrigerant recovery may not be performed when discarded. However, because flammable gases such as propane and toxic gases such as ammonia are dangerous, it is preferable to recover the refrigerant at a disposal site or the like when discarding refrigeration and air conditioning equipment that uses such substances.

[0077] Therefore, when refrigeration and air conditioning equipment in which equipment 5 uses a substance other than fluorocarbons as a refrigerant is transported to the disposal site 40, the refrigerant can be considered to have been recovered, and the fact that the refrigerant has been recovered can be recorded in other fields TBL_Kh.

[0078] <Facility Owner Server Description> The facility owner server 1d has almost the same configuration as the facility staff server 1b, except that the database 12d stores a facility owner table tbl_O instead of a facility staff table tbl_S.

[0079] As described above, work records are accumulated in the facility staff table tbl_S of the facility staff server 1b, the maintenance contractor table tbl_M of the maintenance contractor server 1c, and the facility owner table tbl_O of the facility owner server 1d.

[0080] <Explanation of examples of equipment management system usage> Next, a method for facility staff, maintenance contractors, or facility owners who maintain and manage the same facility 5 to check the work list in the facility management system described above will be specifically explained with reference to Figure 4. Note that the following content is merely an example and is not limited to this.

[0081] First, a facility staff member, maintenance contractor, or facility owner uses a terminal such as a PC or smartphone (not shown) to instruct shared server 1a to display task list screen 6. As a result, task list display unit 10a3 of shared server 1a displays task list screen 6 on terminal screen P of the terminal such as a PC or smartphone (not shown), as shown in FIG.

[0082] For example, record R8 shows that the maintenance company inspected equipment 5 at store B while repairing it. Therefore, the facility staff knows that there is no need to inspect equipment 5 at store B as scheduled in July.

[0083] Furthermore, record R5 reveals that the facility owner performed an inspection of all equipment 5 at Store B at the same time as inventory.

[0084] Therefore, facility staff will know that they do not need to carry out the inventory and inspection work scheduled for December for facility 5 at store B. In this way, it is possible to avoid duplicate work between businesses.

[0085] Furthermore, because of the display 6g indicating that ID03B has been disposed of, the facility owner can know that ID03B has been disposed of without receiving a call from the maintenance company, and can therefore proceed with the inventory work without delay.

[0086] In addition, a 6-hour display suggesting inspection work allows facility staff to know the need for inspection work without being contacted by a maintenance company.

[0087] The inspection suggestion unit 10a4 may display the display 6h and automatically place an order for repairs with a maintenance company. This automatic ordering can be achieved, for example, by storing in advance in the shared server 1a the email addresses and telephone numbers of the maintenance companies and the types of equipment 5 that the maintenance companies can handle. The inspection suggestion unit 10a4 then references the name and model of the equipment 5 based on the equipment ID that has been repaired (see FIG. 3(a)), determines the maintenance company to contact based on that information, and sends an email or SNS message requesting repairs along with information such as the equipment ID, installation location, and model (see FIG. 3(a)).

[0088] Incidentally, in accordance with the repair request in record R6 shown in Figure 4, it is displayed that the maintenance company has carried out repair work, as shown in record R7. At this time, the facility staff member who receives the report of the repaired equipment 5 from the maintenance company must approve whether the reported equipment 5 matches the equipment 5 that was actually repaired. However, by looking at record R7, the facility staff member can identify the equipment 5 that was the target of repair by the common device ID "ID04A" (the device ID that the maintenance company read with the handheld terminal 3 or the like when carrying out the repair work). Therefore, the facility staff member does not need to go and see the actual repaired equipment 5 to approve whether the reported equipment 5 matches the equipment 5 that was actually repaired.

[0089] Records R4 and R6 are checked, and based on the fact that repair work by a maintenance company at store A has reached two times within one year, a display 6h suggesting inspection work to facility staff is displayed on the work list screen 6. By doing this, an inspection can be suggested for equipment 5 at store A that may be in a bad condition.

[0090] As described above, in the present invention, first, facility staff server 1b, maintenance company server 1c, and facility owner server 1d accumulate work records including a common device ID read from active RFID 5a or the like attached to equipment 5. Then, shared server 1a acquires predetermined information including the common device ID from the work records of facility staff server 1b, maintenance company server 1c, and facility owner server 1d, and combines and displays them as a list.

[0091] This allows each business to easily understand the outline of each other's work, avoiding duplicate work, and easily identifying the equipment that has been worked on.

[0092] Therefore, according to the present invention, it is possible to provide a facility management system that easily integrates databases and makes management work easier.

[0093] It should be noted that the contents shown in this embodiment are merely examples, and various modifications and changes are possible within the scope of the gist of the present invention as defined in the claims.

[0094] For example, in this embodiment, as shown in FIG. 1, the shared server 1a, the facility staff server 1b, the maintenance company server 1c, and the facility owner server 1d are each provided as separate servers, but all or part of these may be constructed within a single server.

[0095] Furthermore, in this embodiment, the shared server 1a acquires information from all of the facility staff server 1b, the maintenance company server 1c, and the facility owner server 1d, but it may also acquire information from only two or more of the servers, such as the facility staff server 1b and the maintenance company server 1c.

[0096] Furthermore, in this embodiment, the positions of the access point 2 and the handy terminal 3 are obtained by GPS and transmitted, but a location (for example, "Store A," "food section," etc.) may be set in the access point 2 or the handy terminal 3 and transmitted. Furthermore, since the installation location of the equipment 5 can be determined by referring to the device information table TBL_K of the shared server 1a, the access point 2 and the handy terminal 3 do not necessarily have to transmit their positions. However, since work is not always performed at the installation location and the installation location may have unintentionally changed from the device information table TBL_K, it is preferable to transmit the positions.

[0097] Similarly, in this embodiment, the access point 2 and the handy terminal 3 transmit the timestamp, but the timestamp may be obtained from the built-in clock of the access point 2 or the handy terminal 3 and transmitted. Alternatively, the facility staff server 1b, the maintenance company server 1c, and the facility owner server 1d may obtain the time in their servers.

[0098] In addition, although the present embodiment shows a case where there are multiple facilities such as "Store A" and "Store B" as the facility 4, there may be only one facility. Also, any facility such as a commercial facility, an office building, or an amusement park may be used.

[0099] In this embodiment, the equipment 5 may be of any type, such as water supply and drainage equipment, electrical equipment, firefighting equipment, or refrigeration and air conditioning equipment.

[0100] In addition, in this embodiment, the active RFID 5a and the barcode 5b are used as media for storing the device ID, but this is not limitative and may be, for example, a passive RFID or an IC tag. [Explanation of symbols]

[0101] 1a Shared Server 1b Facility staff server (business server) 1c Maintenance company server (business server) 1d Facility owner server (business server) 2 Access point (reader) 3 Handheld terminal (reading device) 5 Equipment 5a Active RFID (identification tag) 5b Barcode (identification tag) TBL_S Facility staff table (database) TBL_Sa Store (Location Information) TBL_Sb Device ID (identifier) TBL_Sc Date TBL_Sd Work details TBL_M Maintenance company table (database) TBL_Ma Store (Location Information) TBL_Mb Device ID (identifier) TBL_Mc Date TBL_Md Work details TBL_O Facility Owner Table (Database) TBL_Oa Store (Location Information) TBL_Ob Device ID (identifier) TBL_Oc Date TBL_Od Work details

Claims

1. In a facility management system in which reading devices used by a plurality of business operators who maintain and manage the same facility, a plurality of business servers corresponding to the plurality of business operators, and a shared server shared by the plurality of business servers are connected via a network, An identification tag holding an identifier for identifying the equipment is attached to the equipment, the reading device reads the identifier from the identification tag when the plurality of businesses perform work on the facility; the business entity server stores a work record including the identifier read by the reading device, the work record further including the content of the work and the date on which the work was performed; The shared server obtains at least the identifier, the content of the work, and the date the work was performed from two or more of the multiple business servers, combines them, and displays them on a specified terminal screen.

2. The business server further receives and stores the location of the reader when the reader reads the identifier from the reader, The facility management system according to claim 1 , wherein the shared server further acquires the location, combines the location, and displays the location on the predetermined terminal screen.

3. 2. The facility management system according to claim 1, wherein the business server further receives from the reading device the date when the reading device reads the identifier as a timestamp and stores this as the date when the work was performed.

4. The facility management system according to claim 1 , wherein the identification tag is at least one of a one-dimensional barcode and a two-dimensional barcode.

5. The facility management system according to claim 1 , wherein the identification tag is an active RFID tag.

6. 2. The facility management system of claim 1, wherein the shared server further proposes inspection work when the number of times a specified work content is performed reaches a specified number within a specified period in the work records stored in the multiple business operator servers.

7. In an equipment management method, a plurality of reading devices used by a plurality of business operators who maintain and manage the same equipment, a plurality of business servers corresponding to the plurality of business operators, and a shared server shared by the plurality of business servers are connected via a network, When the plurality of businesses perform work on the facility, the reading device reads an identification tag attached to the facility, the identification tag holding an identifier for identifying the facility; The business entity server stores a work record including the identifier read by the reading device, and further including the content of the work and the date on which the work was performed; a step in which the shared server acquires at least the identifier, the content of the work, and the date the work was performed from two or more of the plurality of business servers, combines the information, and displays it on a specified terminal screen.

Images