JP2021140718A - Inspection date data generation device, inspection date data generation method, and inspection date data generation program - Google Patents

Abstract

To provide an inspection date data generation device and the like capable of generating data for the next inspection date using information on inspection record.SOLUTION: An inspection date data generation device in an embodiment performs the steps of: (1) acquiring an equipment CD, an inspection details CD, and work implementation date associated with a property CD specified on an equipment inspection date data output screen from work schedule implementation data including the work implementation date, for each combination of the property CD, the equipment CD, and the inspection details CD; (2) acquiring the inspection cycle linked with the property CD specified on the screen and the equipment CD acquired in the (1) from an equipment master that includes the property CD, equipment CD, and inspection cycle; (3) acquiring a combination in which the next inspection date obtained by adding the inspection cycle acquired in the (2) to the work implementation date acquired in the (1) is within the period specified on the screen; and (4) generating equipment inspection date data that includes a combination of the property CD, the equipment CD, and the inspection details CD acquired in the (3), and the next inspection date corresponding to the combination.SELECTED DRAWING: Figure 14

Description

The present invention relates to an inspection date data generator, an inspection date data generation method, and an inspection date data generation program.

Patent Document 1 discloses an inspection information processing apparatus capable of reducing the labor required when creating an inspection table for inspection of equipment (see paragraph 0006 of Patent Document 1).

Japanese Unexamined Patent Publication No. 2019-095947

However, depending on the technique described in Patent Document 1, there is a problem that it is not possible to efficiently grasp and manage the next inspection date for equipment in a building or the like.

The present invention has been made in view of the above problems, and is an inspection date data generator capable of generating data on the next inspection date by using the inspection record information, an inspection date data generation method, and an inspection date data generation method. The purpose is to provide an inspection date data generation program.

In order to solve the above-mentioned problems and achieve the object, the inspection date data generator according to the present invention is provided with a control unit, and the inspection date data including the next inspection date, which is the next inspection date of the equipment in the property. This is an inspection date data generator for generating the above, and the control unit identifies the property, the property identification data for identifying the property, the equipment identification data for identifying the equipment, and the inspection contents for identifying the inspection contents. For each combination of identification data, the property identification data specified on the screen for instructing the generation of the inspection due date data is linked from the inspection execution data including the inspection implementation latest date, which is the latest date when the inspection was performed. Equipment including equipment identification data, inspection content identification data, implementation date acquisition means for acquiring the latest inspection implementation date, property identification data, equipment identification data, and inspection cycle, which is a cycle for each equipment related to the inspection. The inspection cycle acquisition means that acquires the inspection cycle associated with the property identification data specified on the screen and the equipment identification data acquired by the implementation date acquisition means from the master, and the inspection implementation acquired by the implementation date acquisition means. Acquisition of inspection target to acquire the combination in which the next inspection date calculated by adding the inspection cycle acquired by the inspection cycle acquisition means on the latest day is within the period specified on the screen is acquired from the inspection execution data. The inspection date data including the means, the combination of the property identification data, the equipment identification data, and the inspection content identification data acquired by the inspection target acquisition means, and the calculated next inspection date corresponding to the combination. It is characterized in that it is provided with a means for generating an inspection date to be generated.

Further, the inspection date data generation method according to the present invention is an inspection date for generating inspection date data including the next inspection date, which is the next date for inspection of equipment in the property, which is executed by an information processing device provided with a control unit. A data generation method, which is executed by the control unit, which is property identification data for identifying the property, equipment identification data for identifying the equipment, and inspection content identification data for identifying the inspection content. Equipment associated with the property identification data specified on the screen for instructing the generation of the inspection due date data from the inspection implementation data including the inspection implementation latest date, which is the latest date of the inspection, for each combination of From the equipment master including the identification data, the inspection content identification data, the implementation date acquisition step for acquiring the inspection implementation latest date, the property identification data, the equipment identification data, and the inspection cycle which is the cycle for each equipment related to the inspection. , The inspection cycle acquisition step that acquires the inspection cycle associated with the property identification data specified on the screen and the equipment identification data acquired in the implementation date acquisition step, and the inspection implementation latest date acquired in the implementation date acquisition step. The next inspection date calculated by adding the inspection cycle acquired in the inspection cycle acquisition step is within the period specified on the screen, and the combination is acquired from the inspection execution data with the inspection target acquisition step. Generates the inspection date data including the combination of the property identification data, the equipment identification data, and the inspection content identification data acquired in the inspection target acquisition step, and the calculated next inspection date corresponding to the combination. It is characterized by including an inspection date generation step.

Further, the inspection date data generation program according to the present invention generates inspection date data including the next inspection date, which is the next inspection date of the equipment in the property, to be executed by the information processing apparatus provided with the control unit. It is a due date data generation program, and is to be executed by the control unit, property identification data for identifying the property, equipment identification data for identifying the equipment, and inspection contents for identifying the contents of the inspection. For each combination of identification data, the property identification data specified on the screen for instructing the generation of the inspection due date data is linked from the inspection execution data including the inspection implementation latest date, which is the latest date when the inspection was performed. Equipment including equipment identification data, inspection content identification data, implementation date acquisition step to acquire the latest inspection implementation date, the property identification data, the equipment identification data, and the inspection cycle, which is the cycle for each equipment related to the inspection. From the master, the inspection cycle acquisition step that acquires the property identification data specified on the screen and the inspection cycle associated with the equipment identification data acquired in the implementation date acquisition step, and the inspection implementation acquired in the implementation date acquisition step Acquisition of inspection target to acquire the combination in which the next inspection date calculated by adding the inspection cycle acquired in the inspection cycle acquisition step on the latest day is within the period specified on the screen is acquired from the inspection execution data. The inspection date data including the step, the combination of the property identification data, the equipment identification data, and the inspection content identification data acquired in the inspection target acquisition step, and the calculated next inspection date corresponding to the combination. It is characterized by including an inspection date generation step to be generated.

According to the present invention, there is an effect that data of the next inspection date can be generated by using the inspection record information.

FIG. 1 is a block diagram showing an example of the configuration of the inspection date data generation device. FIG. 2 is a diagram showing an example of the equipment master. FIG. 3 is a diagram showing an example of the property master. FIG. 4 is a diagram showing an example of contract basic information data, contract cost detail data, and contract cost detailed data. FIG. 5 is a diagram showing an example of an input screen for generating contract basic information data. FIG. 6 is a diagram showing an example of an input screen for generating contract cost item data. FIG. 7 is a diagram showing an example of an input screen for generating contract cost detailed data. FIG. 8 is a diagram showing an example of an input screen for generating contract cost detailed data. FIG. 9 is a diagram showing an example of the equipment search screen. FIG. 10 is a diagram showing an example of equipment inspection scheduled data. FIG. 11 is a diagram showing an example of an output screen of equipment inspection schedule data. FIG. 12 is a diagram showing an example of work schedule implementation data. FIG. 13 is a diagram showing an example of a work progress input screen for generating work schedule execution data. FIG. 14 is a diagram showing an example of equipment inspection date data. FIG. 15 is a diagram showing an example of an output screen of equipment inspection date data.

Hereinafter, embodiments of an inspection date data generation device, an inspection date data generation method, and an inspection date data generation program according to the present invention will be described in detail with reference to the drawings. The present invention is not limited to the present embodiment. Hereinafter, a specific configuration and operation will be described.

[1. composition]
An example of the configuration of the inspection date data generation device 100 according to the present embodiment will be described with reference to FIG. FIG. 1 is a block diagram showing an example of the configuration of the inspection date data generation device 100.

The inspection date data generation device 100 is a commercially available desktop personal computer. It should be noted that the inspection date data generator 100 is not limited to a stationary information processing device such as a desktop personal computer, but a commercially available notebook personal computer, a PDA (Personal Digital Assistants), a smartphone, a tablet personal computer, and the like are carried. It may be a type information processing device.

The inspection date data generation device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each part of the inspection date data generation device 100 is communicably connected via an arbitrary communication path.

The communication interface unit 104 connects the inspection date data generation device 100 to the network 300 so as to be communicable via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with another device via a communication line. Here, the network 300 has a function of connecting the inspection date data generation device 100 and the server 200 so as to be able to communicate with each other, and is, for example, the Internet, a LAN (Local Area Network), or the like. Data of various masters and the like, which will be described later, may be stored in the server 200, for example.

An input device 112 and an output device 114 are connected to the input / output interface unit 108. As the output device 114, a speaker or a printer can be used in addition to a monitor (including a home television). As the input device 112, in addition to a keyboard, a mouse, and a microphone, a monitor that cooperates with the mouse to realize a pointing device function can be used. In the following, the output device 114 may be referred to as a monitor 114, and the input device 112 may be referred to as a keyboard 112 or a mouse 112.

Various databases, tables, files, and the like are stored in the storage unit 106. In the storage unit 106, a computer program for giving an instruction to a CPU (Central Processing Unit) in cooperation with an OS (Operating System) to perform various processes is recorded. As the storage unit 106, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, or the like can be used.

The storage unit 106 may, for example, use the equipment master 106a, the property master 106b, the basic contract information data 106c, the contract cost detail data 106d, the contract cost detailed data 106e, the equipment inspection schedule data 106f, and the inspection execution data. It includes 106 g of scheduled work implementation data and 106 h of equipment inspection date data as inspection date data.

According to the inspection date data generation device 100 according to the present embodiment, it is possible to generate equipment inspection date data 106h including the next inspection date, which is the next inspection date of the equipment in the property. As a specific situation, for example, a contractor (for example, a building maintenance contractor) entrusted with the inspection of the equipment by the client becomes the main contractor, and the main contractor asks the subcontractor who is the ordering party to install the equipment. It is assumed that the inspection will be subcontracted. Therefore, the user of the inspection date data generation device 100 according to the present embodiment is, for example, the prime contractor (for example, a building maintenance contractor).

As shown in FIG. 2, the equipment master 106a includes, for example, property identification data (property CD) for identifying the property, equipment identification data (equipment CD and equipment name) for identifying the equipment, and the above. It includes equipment type identification data (equipment type) for identifying the type of equipment, an inspection cycle (inspection deadline) which is a cycle for each equipment related to the inspection, and the like.

Here, the equipment identification data (equipment CD and equipment name) can be searched and displayed by designating the property identification data (property CD) from the equipment search screen shown in FIG. In the equipment search screen shown in FIG. 9, it is also possible to display only the equipment associated with the property selected in the contract basic information data 106c described later.

As shown in FIG. 3, the property master 106b includes, for example, the property identification data (property CD and property name) and the like.

As shown in FIG. 4, the contract basic information data 106c includes, for example, contract identification data (contract NO) for identifying a contract between the client and the prime contractor, and a project within the contract. Project identification data (project name) for identification, contractor identification data (contractor) for identifying the client contractor, property identification data (property CD), contract period, and supervising department , Etc. are included. The contract basic information data 106c can be generated, for example, by inputting the contract period, the property, the contract, and the like from the contract input screen shown in FIG.

The contract cost item data 106d is data of items related to the cost of the order. As shown in FIG. 4, the contract cost detail data 106d includes, for example, the contract identification data (contract NO), the detail identification data (row), and the supplier identification data (supplier) for identifying the supplier. , The order period, the inspection content identification data (business) for identifying the inspection content, the order amount, the equipment identification data (equipment CD), and the like. The contract cost detail data 106d can be generated, for example, by inputting the contract supplier, business, monthly amount, target equipment, and the like from the contract input screen shown in FIG.

The contract cost detailed data 106e is detailed data regarding the cost of the order. As shown in FIG. 4, the contract cost detailed data 106e is, for example, a payment time (work) which is a time to pay the contract identification data (contract NO), the detail identification data (row), and the cost of the order. Month), the order amount (payment amount), and the like. The contract cost detailed data 106e can be generated, for example, by inputting a monthly payment amount or the like from the contract input screen shown in FIGS. 7 and 8.

The equipment inspection scheduled data 106f is data including the scheduled inspection time, which is the scheduled inspection time. As shown in FIG. 10, the equipment inspection scheduled data 106f includes, for example, the property identification data (property), the equipment identification data (equipment), the inspection content identification data (content), the inspection scheduled time, and the like. Etc. are included.

The work schedule implementation data 106g is data in which work record information with respect to the schedule information is input. As shown in FIG. 12, the work schedule implementation data 106g includes, for example, the property identification data (property), the supplier identification data (supplier), the equipment identification data (equipment), and the inspection content identification data. Includes (contents), work month, scheduled work date, the latest date of inspection (work implementation date), which is the latest date when the inspection was carried out, items to be sent, and the like. The work schedule execution data 106g can be generated, for example, by inputting the work execution date for the work schedule from the work progress input screen shown in FIG.

The equipment inspection due date data 106h is the data to be finally generated in the present embodiment, and includes the next inspection due date, which is the next due date of the inspection. As shown in FIG. 14, the equipment inspection date data 106h includes, for example, the property identification data (property), the equipment identification data (equipment), the equipment type identification data (equipment type), and the inspection content identification. Data (work content), the latest inspection implementation date (work implementation), inspection cycle (inspection deadline), next inspection date, contract identification data (contract number), order amount, and order amount (Order amount), the supplier identification data (supplier), precautions at the time of ordering, the items to be sent, and the like.

The control unit 102 is a CPU or the like that collectively controls the inspection date data generation device 100. The control unit 102 has an internal memory for storing a control program such as an OS, a program that defines various processing procedures, required data, and the like, and performs various information processing based on these stored programs. Run.

The control unit 102 is functionally conceptually, for example, (1) equipment acquisition unit 102a, (2) inspection content acquisition unit 102b, (3) payment time acquisition unit 102c, and (4) inspection schedule generation unit 102d. The inspection is carried out for each combination of (5) property identification data for identifying the property, equipment identification data for identifying the equipment, and inspection content identification data for identifying the content of the inspection. Inspection implementation data including the latest inspection date, which is the latest date, equipment identification data, inspection content identification data, and inspection implementation linked to the property identification data specified on the screen for instructing the generation of the inspection date data. An equipment master that includes an implementation date acquisition unit 102e as an implementation date acquisition means for acquiring the latest date, and (6) the property identification data, the equipment identification data, and an inspection cycle that is a cycle for each equipment related to the inspection. The inspection cycle acquisition unit 102f as an inspection cycle acquisition means for acquiring the inspection cycle associated with the property identification data specified on the screen and the equipment identification data acquired by the implementation date acquisition means, and (7) the implementation. The combination in which the next inspection date calculated by adding the inspection cycle acquired by the inspection cycle acquisition means on the latest day of the inspection acquired by the date acquisition means is within the period specified on the screen. 102g of the inspection target acquisition unit as the inspection target acquisition means acquired from the inspection implementation data, and (8) the combination of the property identification data, the equipment identification data, and the inspection content identification data acquired by the inspection target acquisition means, and the combination thereof. The inspection date generation unit 102h as an inspection date generation means for generating the inspection date data including the calculated next inspection date and the corresponding next inspection date is provided.

The equipment acquisition unit 102a is a screen for instructing the generation of equipment inspection scheduled data 106f from the equipment master 106a (see FIG. 2) including the property identification data (property CD) and the equipment identification data (equipment CD). (See FIG. 11), the equipment identification data (equipment CD) associated with the property identification data (property CD) specified in is acquired.

The inspection content acquisition unit 102b acquires equipment from the contract cost detail data 106d (see FIG. 4) including the equipment identification data (equipment CD), the inspection content identification data (business), and the detail identification data (row). The inspection content identification data (business) and the detail identification data (row) associated with the equipment identification data (equipment CD) acquired by the unit 102a are acquired.

The payment time acquisition unit 102c receives the detail identification data (detail identification data 102b) acquired by the inspection content acquisition unit 102b from the contract cost detailed data 106e (see FIG. 4) including the detail identification data (row) and the payment time (working month). Get the payment time (work month) associated with the line). The payment time acquisition unit 102c is associated with the detail identification data (row) acquired by the inspection content acquisition unit 102b from the contract cost detailed data 106e (see FIG. 4), and is designated on the screen (see FIG. 11). You may get the payment time that belongs to the period.

The inspection schedule generation unit 102d includes the property identification data (property CD) specified on the screen (see FIG. 11), the equipment identification data (equipment CD) in the contract cost detail data 106d (see FIG. 4), inspection details, and the like. For each combination of inspection content identification data (business) acquired by the acquisition unit 102b, equipment inspection schedule data 106f including the payment time acquired by the payment time acquisition unit 102c as the inspection schedule time is generated.

The implementation date acquisition unit 102e includes the work including the latest inspection implementation date (work implementation date) for each combination of the property identification data (property), the equipment identification data (equipment), and the inspection content identification data (content). From the scheduled implementation data 106g (see FIG. 12), the equipment identification data (equipment) and inspection associated with the property identification data (property) specified on the screen (see FIG. 15) for instructing the generation of the equipment inspection date data 106h. Acquire content identification data (contents) and the latest inspection implementation date (work implementation date).

The inspection cycle acquisition unit 102f can display the screen (FIG. 15) from the equipment master 106a (see FIG. 2) including the property identification data (property CD), the equipment identification data (equipment CD), and the inspection cycle (inspection deadline). The inspection cycle (inspection deadline) associated with the property identification data (property CD) specified in (see) and the equipment identification data (equipment CD) acquired by the implementation date acquisition unit 102e is acquired.

The inspection target acquisition unit 102g is the next inspection calculated by adding the inspection cycle (inspection deadline) acquired by the inspection cycle acquisition unit 102f to the latest inspection implementation date (work implementation date) acquired by the inspection target acquisition unit 102e. The combination (= combination of the property identification data (property), the equipment identification data (equipment), and the inspection content identification data (content)) whose due date is within the period specified on the screen (see FIG. 15). , Obtained from work schedule implementation data 106 g (see FIG. 12).

The inspection date generation unit 102h is a combination of the property identification data (property), the equipment identification data (equipment), and the inspection content identification data (contents) acquired by the inspection target acquisition unit 102g, and the calculated above-mentioned calculation corresponding to the combination. The equipment inspection date data 106h (see FIG. 14) including the next inspection date is generated.

[2. Specific example of processing]
In this item, a specific example of the process according to this embodiment will be described. In this item, first, the generation of the equipment inspection schedule data 106f as a preliminary preparation will be described in [2-1], and then the generation of the equipment inspection date data 106h, which is the data to be finally generated in the present embodiment, will be described. This will be described in [2-2]. In this item, the equipment master 106a is described with the contents shown in FIG. 2, and the contract basic information data 106c, the contract cost detailed data 106d, and the contract cost detailed data 106e are explained in advance with the contents shown in FIG. do.

[2-1: Generation of equipment inspection schedule data 106f]
In this item, the generation of the equipment inspection schedule data 106f will be specifically described with reference to FIGS. 2, 4, 10, and 11.

[2-1-1. Equipment acquisition process]
First, it is assumed that "2019" is specified as the year and "BK001: XX building" is specified as the property by the operator on the output screen (see FIG. 11) of the equipment inspection schedule data 106f.

In this case, the equipment acquisition unit 102a has "SB001: septic tank 1 (type: A000-1)" and "SB002: sprinkler equipment" as equipment linked to "BK001: XX building" from the equipment master 106a in FIG. , "SB003: Fire extinguisher", "SB004: Indoor fire hydrant equipment" and "SB005: Elevator No. 2".

[2-1-2. Inspection details acquisition process]
Next, the inspection content acquisition unit 102b provides the work "firefighting equipment inspection work" and the line "firefighting equipment inspection work" as information associated with "SB002: sprinkler equipment" acquired by the equipment acquisition unit 102a from the contract cost detail data 106d in FIG. 2 ”is acquired, and the work“ firefighting equipment inspection work ”and line“ 3 ”are acquired as information linked to“ SB004: indoor fire hydrant equipment ”acquired by the equipment acquisition unit 102a.

[2-1-3. Payment time acquisition process]
Next, the payment time acquisition unit 102c is linked to the line "2" acquired by the inspection content acquisition unit 102b from the contract cost detailed data 106e in FIG. 4, and is specified in the output screen of FIG. 11 in FY2019. Acquire 2019/04 and 2019/10 as the payment time to which it belongs. Further, the payment timing acquisition unit 102c is linked to the line "3" acquired by the inspection content acquisition unit 102b from the contract cost detailed data 106e in FIG. 4, and belongs to the fiscal year 2019 specified on the output screen in FIG. Get 2019/06 and 2019/12 as payment time.

[2-1-4. Inspection schedule generation process]
Finally, the inspection schedule generation unit 102d includes the property “BK001: ○○○ building” specified on the output screen of FIG. 11, the equipment “SB002: sprinkler equipment” in the contract cost detail data 106d of FIG. 4, and the inspection contents. Regarding the combination of the work "firefighting equipment inspection work" acquired by the acquisition unit 102b, the payment time 2019/04 and 2019/10 acquired by the payment time acquisition unit 102c are included as the scheduled inspection time, and on the output screen of FIG. A combination of the designated property "BK001: XX Building", the equipment "SB004: indoor fire hydrant equipment" in the contract cost statement data 106d in Fig. 4, and the work "firefighting equipment inspection work" acquired by the inspection content acquisition department 102b. For, the equipment inspection schedule data 106f (see FIG. 10) including the payment timings 2019/06 and 2019/12 acquired by the payment timing acquisition unit 102c as the scheduled inspection timings is generated.

[2-2: Generation of equipment inspection date data 106h]
In this item, the generation of the equipment inspection date data 106h will be specifically described with reference to FIGS. 12 to 15. Regarding the "property", "supplier", "equipment", "content" and "work month" in the work schedule implementation data 106g of FIG. 12, the contract cost detail data 106d of FIG. 4 and the generated equipment inspection of FIG. 10 Information in the schedule data 106f and the like is automatically set. On the other hand, information is input by the operator from the work progress input screen shown in FIG. 13 for the "scheduled work date", "work execution date", and "item to be sent" in the work schedule execution data 106g shown in FIG. .. In this item, the description will proceed on the premise that 106 g of work schedule implementation data having the contents shown in FIG. 12 has been generated in advance.

[2-2-1. Implementation date acquisition process]
First, on the output screen of the equipment inspection date data 106h (see FIG. 15), the operator specifies "2019 / 10-2019 / 12" as the inspection date, and "BK001: XX Building" as the property. It is assumed that "firefighting equipment" is designated as the equipment type and "building management department 1" is designated as the department.

In this case, the implementation date acquisition unit 102e uses the equipment "SB002: sprinkler equipment" and the content "firefighting equipment inspection" as information linked to the property "BK001: XX building" from the work schedule implementation data 106g in FIG. And the work implementation date "2019/4/16", the equipment "SB004: indoor fire hydrant equipment", the content "firefighting equipment inspection" and the work implementation date "2019/6/10" will be acquired.

[2-2-2. Inspection cycle acquisition process]
Next, the inspection cycle acquisition unit 102f is the equipment acquired from the equipment master 106a of FIG. 2 by the property “BK001: ○○○ building” designated on the output screen (see FIG. 15) and the implementation date acquisition unit 102e. Acquired "6 months" as the inspection deadline associated with "SB002: Sprinkler equipment", and acquired the property "BK001: XX Building" and the implementation date, etc. specified on the output screen (see Fig. 15). The inspection deadline associated with the equipment "SB004: Indoor fire hydrant equipment" acquired in 102e is also acquired as "6 months".

[2-2-3. Inspection target acquisition process]
Next, the inspection target acquisition unit 102g acquires a combination of properties, equipment, and contents whose next inspection date is likely to come from the work schedule implementation data 106g shown in FIG.

Specifically, when the inspection deadline "6 months" acquired by the inspection cycle acquisition unit 102f is added to the work implementation date "2019/4/16" acquired by the implementation date acquisition unit 102e, the property "BK001: ○○" ○ The next inspection date for the "firefighting equipment inspection" for the equipment "SB002: sprinkler equipment" in the "building" will be "2019/10/16". Similarly, if the inspection deadline "6 months" acquired by the inspection cycle acquisition unit 102f is added to the work implementation date "2019/6/10" acquired by the implementation date acquisition unit 102e, the property "BK001: ○○○ building" The next inspection date of "Firefighting equipment inspection" for the equipment "SB004: Indoor fire hydrant equipment" in "" will be "2019/12/10".

Here, the next inspection dates "2019/10/16" and "2019/12/10" are both the periods of the inspection dates "2019 / 10-2019 / 12" specified on the output screen (see FIG. 15). Inside. In this case, the inspection target acquisition unit 102g is the property "BK001: ○○○ building" and the equipment "SB002: sprinkler equipment" whose next inspection date is "2019/10/16" from the work schedule implementation data 106g in FIG. , Acquire the work content "Firefighting equipment inspection" and the item to be sent "No abnormality". In addition, the inspection target acquisition unit 102g is the property "BK001: ○○○ building" and the equipment "SB004: indoor fire hydrant equipment" whose next inspection date is "2019/12/10" from the work schedule implementation data 106g in Fig. 12. , Acquire the work content "Firefighting equipment inspection" and the item to be sent "Key returned".

[2-2-4. Inspection date generation profit processing]
Finally, the inspection date generation unit 102h is the property "BK001: ○○○ building" acquired by the inspection target acquisition unit 102g, the equipment "SB002: sprinkler equipment", the work content "firefighting equipment inspection", and the item to be sent "no abnormality". Including the combination of the above and the calculated next inspection date "2019/10/16" corresponding to the combination, the property "BK001: XX Building", the equipment "SB004:" acquired by the inspection target acquisition department 102g. Equipment inspection date data 106h including the combination of "indoor fire hydrant equipment", work content "firefighting equipment inspection" and sent item "key returned", and the calculated next inspection date "2019/12/10" corresponding to the combination. (See FIG. 14) is generated.

[3. Summary of this embodiment]
As described above, according to the inspection date data generation device 100 according to the present embodiment, as mainly explained in [2-2], the inspection performance information (specifically, the work schedule implementation data 106 g). Etc.) can be used to generate data for the next inspection date (specifically, equipment inspection date data 106h).

Here, conventionally, when managing the inspection and repair work schedule for each property equipment on the system, the system is managed separately from the consignment contract information of the equipment management work, and the input and consignment of the annual inspection and repair work schedule. In general, the cost recording schedule was entered separately based on the contract. For this reason, when creating an annual inspection plan for equipment, there were many cases where it was created with reference to the consignment contract information.

Therefore, in the present embodiment, for example, the following 1 and 2 are made possible as described in [2-1].
1. 1. When managing the inspection and repair work history, it can be processed together with the consignment contract information.
2. Property equipment information, work management, and consignment information management can now be linked and managed.

In addition, depending on the equipment, the periodic inspection cycle is stipulated by law, but in the past, the inspection results and the cycle for each equipment were managed separately, so the next inspection deadline is manually managed. There were many cases. For this reason, there is a problem that the inspection is omitted and the advance guidance to the customer is delayed.

Therefore, in the present embodiment, for example, the following 1 to 3 are made possible as described in [2-2].
1. 1. By linking the cycle of equipment information and work information, the next periodic inspection schedule can be calculated.
2. The deadline for the next regular inspection was managed so that the previous contract information could be added.
3. 3. By linking the inspection cycle and inspection results of the equipment to the contract data, it is possible to manage the due date of the next inspection schedule.

As a result, in the present embodiment, for example, it has become possible to manage the next periodic inspection schedule and carry out sales activities without omissions. In addition, since the contract information of the previous work execution is linked by the mechanism of [2-1], it has become possible to prevent an inappropriate difference in the amount of orders placed and received.

[4. Other embodiments]
In addition to the above-described embodiments, the present invention may be implemented in various different embodiments within the scope of the technical ideas described in the claims.

For example, of each of the processes described in the embodiments, all or part of the processes described as being automatically performed may be manually performed, or all of the processes described as being performed manually. Alternatively, a part thereof can be automatically performed by a known method.

In addition, the processing procedure, control procedure, specific name, information including parameters such as registration data and search conditions of each processing, screen examples, and database configuration shown in the present specification and drawings are not specified unless otherwise specified. Can be changed arbitrarily.

Further, with respect to the inspection date data generation device 100, each component shown in the figure is a functional concept and does not necessarily have to be physically configured as shown in the figure.

For example, with respect to the processing functions included in the inspection date data generation device 100, particularly each processing function performed by the control unit, all or any part thereof is realized by the CPU and a program interpreted and executed by the CPU. It may be realized as hardware by wired logic. The program is recorded on a non-temporary computer-readable recording medium including a programmed instruction for causing the information processing apparatus to execute the process described in the present embodiment, and inspection date data is obtained as necessary. It is read mechanically by the generator 100. That is, a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or an HDD (Hard Disk Drive). This computer program is executed by being loaded into RAM, and cooperates with a CPU to form a control unit.

Further, this computer program may be stored in an application program server connected to the inspection date data generator 100 via an arbitrary network, and all or a part thereof may be downloaded as needed. It is possible.

Further, the program for executing the process described in the present embodiment may be stored in a non-temporary computer-readable recording medium, or may be configured as a program product. Here, the "recording medium" includes a memory card, a USB (Universal Serial Bus) memory, an SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), and an EEPROM (registration). Trademarks) (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magnet-Optical Disk), MO (Magnet-Optical Disk), MO (Magnet-Optical Disc), DVD (Digital), DVD (Digital) It shall include any "portable physical medium".

The "program" is a data processing method described in any language or description method, regardless of the format such as source code or binary code. The "program" is not necessarily limited to a single program, but is distributed as a plurality of modules or libraries, or cooperates with a separate program represented by the OS to achieve its function. Including things. A well-known configuration or procedure can be used for a specific configuration and reading procedure for reading the recording medium in each device shown in the embodiment, an installation procedure after reading, and the like.

Various databases and the like stored in the storage unit are memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and storage means such as optical disks, and are used for various processes and website provision. Stores programs, tables, databases, files for web pages, etc.

Further, the inspection date data generation device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which an arbitrary peripheral device is connected. Further, the inspection date data generation device 100 may be realized by mounting software (including a program or data) that realizes the processing described in the present embodiment on the device.

Further, the specific form of distribution / integration of the device is not limited to the one shown in the drawing, and all or a part thereof may be functionally or physically in an arbitrary unit according to various additions or functional loads. It can be distributed and integrated. That is, the above-described embodiments may be arbitrarily combined and implemented, or the embodiments may be selectively implemented.

The present invention is useful in all industries, but is particularly useful in the building maintenance industry.

100 Inspection date data generator 102 Control unit
102a Equipment acquisition department
102b Inspection details acquisition section
102c Payment time acquisition department
102d Inspection schedule generator
102e Implementation date acquisition department
102f Inspection cycle acquisition unit
102g Inspection target acquisition department
102h Inspection date generation unit 104 Communication interface unit 106 Storage unit
106a Equipment Master
106b Property Master
106c Contract basic information data
106d Contract cost item data
106e Contract cost detailed data
106f Equipment inspection schedule data
106g Work schedule implementation data
106h Equipment inspection date data 108 Input / output interface 112 Input device 114 Output device 200 Server 300 Network

Claims (3)

It is an inspection date data generator that has a control unit and generates inspection date data including the next inspection date, which is the next date for inspection of equipment in the property.
The control unit
For each combination of property identification data for identifying the property, equipment identification data for identifying the equipment, and inspection content identification data for identifying the content of the inspection, on the latest date when the inspection was performed. From the inspection implementation data including the latest inspection implementation date, the equipment identification data, inspection content identification data, and inspection implementation latest date associated with the property identification data specified on the screen for instructing the generation of the inspection due date data are acquired. Means of acquisition of implementation date, etc.
From the equipment master including the property identification data, the equipment identification data, and the inspection cycle which is the cycle for each equipment related to the inspection, the property identification data specified on the screen and the equipment identification acquired by the implementation date and the like acquisition means. Inspection cycle acquisition means to acquire the inspection cycle associated with data,
The combination in which the next inspection date calculated by adding the inspection cycle acquired by the inspection cycle acquisition means on the latest inspection execution date acquired by the inspection execution date acquisition means is within the period specified on the screen. , The inspection target acquisition means acquired from the inspection implementation data,
An inspection that generates the inspection date data including the combination of the property identification data, the equipment identification data, and the inspection content identification data acquired by the inspection target acquisition means and the calculated next inspection date corresponding to the combination. Due date generation means and
To prepare
Inspection date data generator featuring. It is an inspection date data generation method that generates inspection date data including the next inspection date, which is the next date for inspection of equipment in the property, which is executed by an information processing device equipped with a control unit.
Executed by the control unit,
For each combination of property identification data for identifying the property, equipment identification data for identifying the equipment, and inspection content identification data for identifying the content of the inspection, on the latest date when the inspection was performed. From the inspection implementation data including the latest inspection implementation date, the equipment identification data, inspection content identification data, and inspection implementation latest date associated with the property identification data specified on the screen for instructing the generation of the inspection due date data are acquired. Implementation date acquisition steps and
Property identification data specified on the screen and equipment identification acquired in the implementation date acquisition step from the equipment master including the property identification data, the equipment identification data, and the inspection cycle which is the cycle for each equipment related to the inspection. The inspection cycle acquisition step to acquire the inspection cycle associated with the data,
The combination in which the next inspection date calculated by adding the inspection cycle acquired in the inspection cycle acquisition step on the latest inspection execution date acquired in the implementation date acquisition step is within the period specified on the screen. , The inspection target acquisition step to be acquired from the inspection implementation data,
An inspection that generates the inspection date data including the combination of the property identification data, the equipment identification data, and the inspection content identification data acquired in the inspection target acquisition step and the calculated next inspection date corresponding to the combination. Due date generation step and
Including,
Inspection date data generation method characterized by. An inspection date data generation program that generates inspection date data including the next inspection date, which is the next date for inspection of equipment in the property, to be executed by an information processing device equipped with a control unit.
To make the control unit execute
For each combination of property identification data for identifying the property, equipment identification data for identifying the equipment, and inspection content identification data for identifying the content of the inspection, on the latest date when the inspection was performed. From the inspection implementation data including the latest inspection implementation date, the equipment identification data, inspection content identification data, and inspection implementation latest date associated with the property identification data specified on the screen for instructing the generation of the inspection due date data are acquired. Implementation date acquisition steps and
Property identification data specified on the screen and equipment identification acquired in the implementation date acquisition step from the equipment master including the property identification data, the equipment identification data, and the inspection cycle which is the cycle for each equipment related to the inspection. The inspection cycle acquisition step to acquire the inspection cycle associated with the data,
The combination in which the next inspection date calculated by adding the inspection cycle acquired in the inspection cycle acquisition step on the latest inspection execution date acquired in the implementation date acquisition step is within the period specified on the screen. , The inspection target acquisition step to be acquired from the inspection implementation data,
An inspection that generates the inspection date data including the combination of the property identification data, the equipment identification data, and the inspection content identification data acquired in the inspection target acquisition step and the calculated next inspection date corresponding to the combination. Due date generation step and
Including,
An inspection date data generation program characterized by.

Images