Operation management device

Abstract

The client and the team performing the work will share the prerequisites for the task. [Solution] A work management device comprising: precondition acquisition means for obtaining preconditions for work scheduled to be commenced from the client requesting the work; precondition output means for outputting the details of the preconditions to a person in charge of the client requesting the work, who has been determined in advance; precondition approval acquisition means for obtaining approval of the preconditions from the person in charge of the client; recording means for recording the approved preconditions; and approval information output means for outputting the approved preconditions to a person in charge of executing the work.

Description

Technical Field

[0001] The present invention relates to a work management device.

Background Art

[0002] Before performing construction work, it is necessary to share information related to the construction between the person who requests the work (requestor) and the person who executes the work (executor). For example, Patent Documents 1 to 3 disclose systems for sharing information related to construction between the requestor and the executor.

[0003] Patent Document 1 discloses a management system for managing construction information including information related to an initial application required prior to construction. More specifically, in the technology disclosed in Patent Document 1, first, the construction contractor registers construction information in the construction information database from its own computer terminal and requests approval from the management department of the construction client, etc. When the construction contractor registers the construction information, the management system sends an approval request email to the management department of the client, etc. When the management department of the client receives the email, it checks the construction information and approves or rejects it. As described above, the construction contractor can receive approval, etc. from the construction client.

[0004] Patent Document 2 discloses a comprehensive building construction management system including the client, supervisor, and constructor. More specifically, in the technology disclosed in Patent Document 2, the constructor negotiates with the construction company to create construction-related documents (construction process schedule, schedule, etc.) and operates the constructor-side terminal device to input information related to the construction-related documents. The construction-related document data is registered in the recording database of the server unit, and the client and supervisor perform approval operations on the client-side terminal device and the supervisor-side terminal device. As described above, the approval process for the information imposed on the construction-related documents is performed.

[0005] Patent Document 3 discloses a construction management support system that reduces the burden of revision and approval work among multiple contractors, from the client to the contractor, enabling rapid processing and smooth communication between higher and lower-level contractors. In the technology disclosed in Patent Document 3, the construction management support system allows relevant parties to share information such as the name of the building owner, the name of the planned contractor, the name of the selected contractor, as well as design data (design drawings, calculations, and other requests), various government permits and licenses, construction approval request information (approved construction drawings, approved equipment specifications, etc.), construction approval information (approved construction drawings, approved equipment specifications, etc.), design change requests, and design change instructions via the internet, supporting tasks such as approval and storage of drawings involving multiple parties. Furthermore, Patent Document 3 discloses that approval requests are sent via email to higher-level organizations, and these higher-level organizations then perform the approval. [Prior art documents] [Patent Documents]

[0006] [Patent Document 1] Japanese Patent Publication No. 2002-117097 [Patent Document 2] Japanese Patent Publication No. 2009-134685 [Patent Document 3] Japanese Patent Publication No. 2005-108015 [Overview of the project] [Problems that the invention aims to solve]

[0007] However, the methods disclosed in Patent Documents 1-3 do not disclose the approval of prerequisites necessary for carrying out construction work. Therefore, in the methods disclosed in Patent Documents 1-3, the prerequisites are not shared or approved, and the approval process for the work may be insufficient.

[0008] The object of the present invention is to provide a work management device that solves the above-mentioned problems. [Means for solving the problem]

[0009] One aspect of the present invention is a work management device comprising: precondition acquisition means for obtaining preconditions for work scheduled to be commenced from the client requesting the work; precondition output means for outputting the details of the preconditions to a person in charge of the client requesting the work, as determined in advance; precondition approval acquisition means for obtaining approval of the preconditions from the person in charge of the client; recording means for recording the approved preconditions; and approval information output means for outputting the approved preconditions to a person in charge of executing the work. [Effects of the Invention]

[0010] According to the present invention, the preconditions for the work can be shared between the client and the performer. [Brief explanation of the drawing]

[0011] [Figure 1] This figure shows the configuration of the work management system 1 according to this embodiment. [Figure 2] This figure shows an example of the configuration of the work management device 10 according to the first embodiment. [Figure 3] This is a sequence diagram showing the operation of the work management system 1 according to the first embodiment. [Figure 4] This figure shows an example of the configuration of the work management device 10 according to the second embodiment. [Figure 5] This is a sequence diagram showing the approval of the work plan in the second embodiment. [Modes for carrying out the invention]

[0012] <First Embodiment> Embodiments of the present invention will be described in detail below with reference to the drawings. Figure 1 shows the configuration of the work management system 1 according to this embodiment. The work management system 1 comprises a work management device 10, requester devices 11-1 and 11-2, and executioner devices 12-1 and 12-2. The work management device 10 and the requester devices 11-1 and 11-2 can communicate and send and receive data. The work management device 10 and the executioner devices 12-1 and 12-2 can communicate and send and receive data. Hereinafter, when there is no need to distinguish between requester devices 11-1 and 11-2, they will be referred to as requester device 11, and when there is no need to distinguish between executioner devices 12-1 and 12-2, they will be referred to as executioner device 12. The work management device 10 stores the account information of the users of the services to be provided. The account information includes information on whether the user is a requester user or an executioner user. The requester device 11 is a device logged in with the account of a requester user, and the work management device 10 recognizes from the stored account information that the logged-in user is a requester user and provides services to the requester. The execution source device 12 is a device logged in with the execution source user's account. The work management device 10 recognizes from the stored account information that the logged-in user is the execution source user and provides services to the execution source.

[0013] The work management device 10 is a device for managing work. Work can be, for example, work at a construction site or work at a steel mill, but is not particularly limited. The requesting device 11 is a device used by the party requesting the work. The executing device 12 is a device used by the party executing the work. The requesting party is, for example, the client that orders the work. The executing party is, for example, the contractor that receives the work. For example, the executing party is a cooperating company of the party requesting the work.

[0014] In the work management system 1 shown in Figure 1, two requesting devices 11-1 and 11-2 are provided, but one or more requesting devices 11 may be provided in the work management system 1. Also, in the work management system 1 shown in Figure 1, two execution devices 12-1 and 12-2 are provided, but one or more execution devices 12 may be provided in the work management system 1.

[0015] FIG. 2 is a diagram showing an example of the configuration of the work management device 10 according to the first embodiment. The work management device 10 according to the first embodiment includes an acquisition unit 20, an output unit 30, a recording unit 50, and a storage device 60.

[0016] The acquisition unit 20 acquires information from the request source device 11 and the execution source device 12. The output unit 30 outputs information to the request source device 11 and the execution source device 12. The recording unit 50 records information in the storage device 60. The acquisition unit 20 further includes a prerequisite acquisition unit 21 and a prerequisite approval acquisition unit 22. The output unit 30 further includes a prerequisite output unit 31 and an approval information output unit 32. The recording unit 50 further includes an approval prerequisite recording unit 51.

[0017] The prerequisite acquisition unit 21 acquires information (hereinafter referred to as "prerequisite information") regarding the prerequisites before the work scheduled to start from the request source device 11.

[0018] The prerequisite indicates the equipment state required as a prerequisite for starting the work. More specifically, the prerequisites include, for example, a method for avoiding contact with high-temperature substances, low-temperature substances, etc. The prerequisites include, for example, whether gas replacement is required in a gas poisoning risk area. The prerequisites include, for example, whether materials such as air respirators and airline masks are required in a gas poisoning / oxygen deficiency risk area. The prerequisites include, for example, a method for avoiding contact with acids / alkalis. The prerequisites include, for example, the starting conditions for work in the vicinity of a high-voltage charging section.

[0019] The prerequisite output unit 31 outputs the acquired prerequisite information to the request source device 1,1. The request source device 11 as the output destination is a device used by the related person of the request source of the work scheduled to start, which is determined in advance. The request source device 11 as the output destination is a device different from the request source device 11 that acquired the prerequisite information. Note that the prerequisite output unit 31 may output the prerequisite information to the request source device 11 that acquired the prerequisite information.

[0020] The prerequisite approval acquisition means 22 obtains prerequisite approval from the requesting party's device 11.

[0021] The approval prerequisite recording means 51 records the approved prerequisite information in the storage device 60.

[0022] The approval information output means 32 outputs the approved prerequisite information to the execution source device 12. The execution source device 12, which is the output destination, is a device used by the person responsible for executing the work that is scheduled to be started, as determined in advance.

[0023] The requesting device 11 outputs prerequisite information and approval of prerequisites to the work management device 10. The requesting device 11 obtains prerequisite information and approval of prerequisites from the work management device 10.

[0024] The execution source device 12 obtains approved prerequisite information from the work management device 10.

[0025] Furthermore, information regarding the output destination of the prerequisite information may be stored in the storage device 60 in advance. The prerequisite output means 31 may output the prerequisite information to an output destination based on the information stored in the storage device 60.

[0026] Figure 3 is a sequence diagram showing an example of the operation of the work management system 1 according to the first embodiment. In the example shown in Figure 3, an application corresponding to the work is created in advance, and the requesting devices 11-1 and 11-2 and the execution devices 12-1 and 12-2 are granted the authority to access the application. The requesting devices 11-1 and 11-2 and the execution devices 12-1 and 12-2 receive services from the application. The application corresponding to the work is created, for example, when the requesting device 11-1 or 11-2 accesses an application for registering work case information and registers the work case information.

[0027] The services provided by the application differ between the requesting device 11 and the execution device 12. Whether the service is being provided to the requesting device 11 or the execution device 12 is determined by the account logged into the device and the work management device 10 recognizes the stored account information.

[0028] The requesting device 11 is provided with an interface for outputting prerequisite information, but the execution device 12 is not. For example, the display unit of the requesting device 11 shows a button to start the prerequisite output process. When the user of the requesting device 11 uses the requesting device 11 and selects the button to start the prerequisite output process, the display unit of the requesting device 11 shows buttons for selecting the prerequisites required for the current task from the list of task prerequisites, as well as an output button. In the example shown in Figure 3, the requesting device 11-1 is a device used by the user who defines the task prerequisites. The user of the requesting device 11-1 uses the requesting device 11-1 to select the prerequisites required for the current task from the list of task prerequisites and presses the output button to output the prerequisite information to the work management device 10 (step S11).

[0029] The prerequisite acquisition means 21 acquires prerequisite information (step S12). The prerequisite output means 31 outputs the prerequisite information to the requesting device 11 which has been granted permission to access the application (step S13). In the example shown in Figure 3, the prerequisite output means 31 outputs the prerequisite information to the requesting device 11-2. In other words, the prerequisite output means 31 grants the requesting device 11-2 access rights to the said prerequisite information.

[0030] Furthermore, when the requesting device 11 selects the prerequisites required for the current task from the list of prerequisites for the task, it may select a requesting device 11 that has been granted permission to access the application and will be the destination for outputting the prerequisite information. In this case, the prerequisite output means 31 outputs the prerequisite information to the selected requesting device 11.

[0031] The requesting device 11-2 retrieves prerequisite information (step S14). The requesting device 11-2 displays the prerequisite information, an approve button, and a reject button. The user of the requesting device 11-2 reviews the prerequisite information displayed on the requesting device 11-2 and considers whether to approve or reject it.

[0032] Subsequently, when the user of the requesting device 11-2 presses the approval button, the requesting device 11-2 outputs the approval of the prerequisites to the work management device 10 (step S15). The prerequisite approval acquisition means 22 acquires the approval of the prerequisites (step S16). The approval information output means 32 outputs the approved prerequisite information to the execution source devices 12-1 and 12-2, which are execution source devices 12 that have been granted permission to access the application (step S18). In other words, the prerequisite output means 31 grants the execution source devices 12-1 and 12-2 access rights to the approved prerequisite information.

[0033] Furthermore, when the requesting device 11 selects the prerequisites required for the current task from the list of prerequisites for the task, it may select the execution device 12 that is authorized to access the application and will be the output destination for the approved prerequisite information. In this case, the approval information output means 32 outputs the approved prerequisite information to the selected execution device 12.

[0034] The execution source device 12-1 obtains the approved prerequisite information (step S19-1). The execution source device 12-2 obtains the approved prerequisite information (step S19-2). The approved prerequisite information is displayed on execution source devices 12-1 and 12-2. The users of execution source devices 12-1 and 12-2 confirm the prerequisite information displayed on execution source devices 12-1 and 12-2, respectively, and perform their tasks based on the prerequisites.

[0035] In step S15, if the user of the requesting device 11-2 presses the rejection button, the requesting device 11-2 outputs the rejection of the prerequisite to the work management device 10. The requesting device 11-2 may accept input of the reason for rejection. In this case, if the user of the requesting device 11-2 inputs the reason for rejection, the requesting device 11-2 outputs the reason for rejection to the work management device 10. When the prerequisite approval acquisition means 22 acquires the rejection of the prerequisite, the approval information output means 32 notifies the requesting device 11-1 that the prerequisite has been rejected. If the prerequisite approval acquisition means 22 acquires the reason for rejection, the approval information output means 32 may notify the requesting device 11-1 of the reason why the prerequisite was rejected. The requesting device 11-1 displays that the prerequisite has been rejected. The user of the requesting device 11-1 reconsiders the prerequisite.

[0036] In step S13, if the prerequisite output means 31 outputs prerequisite information to multiple requesting devices 11, the approval information output means 32 outputs the approved prerequisite information to the execution device 12 when the prerequisite approval acquisition means 22 obtains approval from the multiple requesting devices 11. The prerequisite approval acquisition means 22 does not necessarily have to obtain approval from all requesting devices 11 that output prerequisite information; the approval information output means 32 may output the approved prerequisite information to the execution device 12 when approval is obtained from a predetermined number of requesting devices 11.

[0037] In the work management system 1 according to the first embodiment, the requesting party can approve the prerequisites for the work and notify the executing party of the approved prerequisites. This allows the requesting party to confirm and approve the prerequisites, share the approved prerequisites with the executing party, and the executing party to perform the work based on the approved prerequisites.

[0038] (Second embodiment) Figure 4 shows an example of the configuration of the work management device 10 according to the second embodiment. The work management device 10 according to the second embodiment includes, in addition to the work management device 10 according to the first embodiment, a work plan acquisition means 23, a work plan approval acquisition means 24, a work plan output means 33, and an approved work plan recording means 52.

[0039] The work plan acquisition means 23 acquires information regarding the work plan created by the execution source (hereinafter referred to as "work plan information") from the execution source device 12.

[0040] The work plan outlines the necessary tasks before commencing work. Work plans include, for example, plans for installing scaffolding and safety fences during work at height. Work plans include, for example, plans for protecting surfaces during work near openings. Work plans include, for example, plans for using cranes and tow trucks. Work plans include, for example, plans for transporting heavy objects.

[0041] The work plan output means 33 outputs the acquired work plan to the requesting device 11 and the execution device 12. The requesting device 11 and the execution device 12, which are the output destinations, are the parties involved in the work request and execution, as determined in advance.

[0042] The work plan approval acquisition means 24 obtains approval of the work plan from the requesting device 11 and the execution device 12.

[0043] The approved work plan recording means 52 records the approved work plan information in the storage device 60.

[0044] In the second embodiment, the approval information output means 32 notifies the execution source device 12 that output the work plan information that the work plan has been approved.

[0045] Figure 5 is a sequence diagram showing the approval of a work plan in the second embodiment. In the example shown in Figure 5, an application corresponding to the work is created in advance, and the requesting devices 11-1 and 11-2 and the execution devices 12-1 and 12-2 are granted permission to access the application.

[0046] The execution source device 12 is provided with an interface for outputting work plan information, but the requesting device 12 is not. For example, the display unit of the execution source device 12 displays a button for starting the work plan output process. When the user of the execution source device 12 uses the execution source device 12 and selects the button for starting the work plan output process, the display unit of the execution source device 12 displays buttons for selecting the work plan for the current task from the work plan list, as well as an output button. In the example shown in Figure 5, the execution source device 12-1 is a device used by the user who defines the work plan. The user of the execution source device 12-1 uses the execution source device 12-1 to select the work plan for the current task from the work plan list and presses the output button to output the work plan information to the work management device 10 (step S21).

[0047] The work plan acquisition means 23 acquires work plan information (step S22). The work plan output means 33 outputs the work plan information to the requesting device 11 and the execution device 12, which have been granted permission to access the application (step S23). In the example shown in Figure 5, the work plan output means 33 outputs the work plan information to the requesting devices 11-1 and 11-2 and the execution device 12-2. In other words, the work plan output means 33 grants the requesting devices 11-1 and 11-2 and the execution device 12-2 access rights to the work plan information.

[0048] Furthermore, when the execution source device 12 selects a work plan for the current task from the work plan list, it may select the requesting device 11 that will be the output destination for prerequisite information from among the requesting devices 11 that have been granted permission to access the application, and select the execution source device 12 that will be the output destination for prerequisite information from among the execution source devices 12 that have been granted permission to access the application. In this case, the work plan output means 33 outputs the prerequisite information to the selected requesting device 11.

[0049] The requesting device 11-1 acquires the work plan information (step S24-1). The requesting device 11-2 acquires the work plan information (step S24-2). The execution device 12-2 acquires the work plan information (step S25). The requesting devices 11-1 and 11-2, and the execution device 12-2, each display the work plan information, an approve button, and a reject button, respectively. The user of each device checks the work plan information displayed on the device and considers whether to approve it or not.

[0050] Subsequently, when the user of requesting device 11-1 presses the approval button, requesting device 11-1 outputs the work plan approval to the work management device 10 (step S26-1). When the user of requesting device 11-2 presses the approval button, requesting device 11-2 outputs the work plan approval to the work management device 10 (step S26-2). When the user of execution device 12-2 presses the approval button, execution device 12-2 outputs the work plan approval to the work management device 10 (step S27).

[0051] The work plan approval acquisition means 24 obtains approval of the work plan from the requesting device 11-1 (step S28-1), obtains approval of the work plan from the requesting device 11-2 (step S28-2), and obtains approval of the work plan from the execution device 12-2 (step S29).

[0052] Subsequently, the approval information output means 32 notifies the execution source device 12-1 that it has obtained approval from all devices that output the work plan information (step S30). The user of the execution source device 12-1 confirms that the work plan has been approved and executes the work based on the work plan.

[0053] The approval of the work prerequisites shown in Figure 3 and the approval of the work plan shown in Figure 5 may be carried out independently. Therefore, in the work management system 1, the approval of the work prerequisites may be carried out after the approval of the work plan, or after the approval of the work prerequisites, or the approval of the work plan and the approval of the work prerequisites may be carried out in parallel.

[0054] In steps S26-1, 26-2, and 27, if the user of requesting device 11-1, requesting device 11-2, or executing device 12-2 presses the rejection button, requesting device 11-1, requesting device 11-2, or executing device 12-2 outputs the rejection of the work plan to the work management device 10. Requesting device 11-1, requesting device 11-2, or executing device 12-2 may accept input of the reason for rejection. In this case, if the user of requesting device 11-1, requesting device 11-2, or executing device 12-2 inputs the reason for rejection, requesting device 11-1, requesting device 11-2, or executing device 12-2 outputs the reason for rejection to the work management device 10.

[0055] When the work plan approval acquisition means 24 obtains a rejection of a prerequisite, the approval information output means 32 notifies the execution source device 12-1 that the work plan has been rejected. If the work plan approval acquisition means 24 obtains a reason for rejection, the approval information output means 32 may also notify the execution source device 12-1 of the reason for the rejection of the work plan. The execution source device 12-1 displays that the work plan has been rejected. The user of the execution source device 12-1 then reconsiders the work plan.

[0056] In step S23, the work plan acquisition means 23 does not necessarily have to obtain approval from all devices that output work plan information. If approval is obtained from the pre-determined requesting device 11 and / or execution device 12, the approval information output means 32 may notify the execution device 12-1 that the work plan has been approved.

[0057] When outputting work plan information to multiple requesting devices 11 and execution devices 12, if the work plan acquisition means 23 obtains approval from the multiple requesting devices 11 and execution devices 12, the approved work plan recording means 52 records the approved work plan information. However, the work plan acquisition means 23 does not necessarily have to obtain approval from all requesting devices 11 and execution devices 12 to which the work plan information was output; the approved work plan recording means 52 may record the approved work plan information only when approval is obtained from a specific requesting device 11 and / or execution device 12.

[0058] In the work management system 1 according to the second embodiment, in addition to the work management system 1 according to the first embodiment, the requesting party and the executing party can also approve the work plan. This allows the work plan to be shared between the executing party and the requesting party, enabling the work to proceed more smoothly.

[0059] <Other Embodiments> Although one embodiment of this invention has been described in detail above with reference to the drawings, the specific configuration is not limited to that described above, and various design changes can be made without departing from the spirit of this invention.

[0060] Some or all of the work management device 10 in the above-described embodiment may be implemented using a computer. In that case, the program for implementing this function may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be loaded into a computer system and executed. Here, "computer system" includes the OS and peripheral hardware. Furthermore, "computer-readable recording medium" refers to portable media such as flexible disks, magneto-optical disks, ROMs, CD-ROMs, and recording devices such as hard disks built into a computer system. In addition, "computer-readable recording medium" may include those that dynamically hold programs for a short period of time, such as communication lines used when transmitting programs via networks such as the Internet or communication lines such as telephone lines, and those that hold programs for a certain period of time, such as volatile memory inside a computer system that acts as a server or client in that case. Furthermore, the above-mentioned program may be for implementing some of the functions described above, and may also be able to implement the above-mentioned functions in combination with programs already recorded in the computer system. Furthermore, some or all of the work management device 10 may be implemented using programmable logic devices such as FPGAs (Field Programmable Gate Arrays). [Explanation of Symbols]

[0061] 1 Work management system, 10 Work management device, 11 Requesting device, 12 Execution device, 20 Acquisition means, 21 Prerequisite acquisition means, 22 Prerequisite approval acquisition means, 23 Work plan acquisition means, 24 Work plan approval acquisition means, 30 Output means, 31 Prerequisite output means, 32 Approval information output means, 33 Work plan output means, 50 Recording means, 51 Approval prerequisite recording means, 52 Approval work plan recording means, 60 Storage device

Claims

1. A means for obtaining preconditions for the work to be commenced from the client requesting the work, A precondition output means that outputs information regarding the preconditions to the person who requested the work as determined in advance, A means for obtaining approval of the preconditions from the parties involved in the request, Recording means for recording information regarding the aforementioned approved preconditions, Approval information output means for outputting the approved preconditions to the person responsible for executing the work, A work management device equipped with the following features.

2. A work plan acquisition means that acquires a work plan from the source that performs the aforementioned work, The task of outputting the work plan to the parties involved in the request and execution of the aforementioned work, as determined in advance. Planning output means, The work plan approval process involves obtaining approval for the work plan from the parties involved in the request and execution of the work plan. Means and The work management device according to claim 1.

3. The work management device according to claim 1 or 2, wherein the aforementioned preconditions include at least one of the following: a method for avoiding contact with high-temperature objects, low-temperature objects, etc., whether gas replacement is necessary in gas poisoning hazard areas, whether materials such as self-contained breathing apparatus and airline masks are necessary in gas poisoning / oxygen deficiency hazard areas, a method for avoiding contact with acids / alkalis, or conditions for commencing work in proximity to high-voltage live parts.

4. The aforementioned work plan includes at least one of the following: a plan for installing scaffolding and safety fences for work at height, a plan for protective measures for work near openings, a plan for using crane and wrecker equipment, and a plan for transporting heavy objects. The work management device according to claim 2.

Images