Construction industry administrative support equipment

Abstract

To support construction companies in performing administrative tasks, including coordination between clients, work sites, and companies, for various tasks, including those that reflect the specific circumstances of construction companies, such as inspections required for compliance with laws and regulations. [Solution] The construction industry administrative agency support device 1 of the present invention comprises a transaction information acquisition unit 112 that acquires transaction information, a communication record acquisition unit 113 that acquires communication records, a data management unit 111 that manages data associating communication records with transaction information, an inspection request command unit 115 that commands the requesting of necessary inspections, a work schedule registration unit 116 that registers work schedules, and a material generation unit 117 that generates materials, and the work schedule registration unit 116 is capable of registering work schedules including the above-mentioned inspections, and the material generation unit 117 is capable of generating materials including communication records and / or work schedules.

Description

[Technical field]

[0001] The present invention relates to a construction business agency support device. [Background technology]

[0002] There is a demand among construction companies to reduce the burden of administrative tasks such as customer support, data registration, and financial operations, and to focus on core operations. By outsourcing specific tasks to external specialists through Business Process Outsourcing (BPO), construction companies can reduce fixed costs related to administrative tasks, concentrate resources on core operations, and flexibly respond to changes in business scale.

[0003] However, the introduction of BPO can have various implementation hurdles, such as implementation costs, communication costs, and operation costs. Implementation costs include, for example, the time and financial costs involved in business process analysis, system integration, and staff training. Communication costs include, for example, the cost of conveying the content of a construction company's work to specialists. Operational costs include, for example, personnel costs for staff. Therefore, there is a demand for technology that supports the outsourcing of administrative work at construction companies.

[0004] Regarding technology to support administrative work at construction companies, Patent Document 1 discloses a method of supporting procurement of construction materials and equipment in which a support center centrally manages transactions of construction materials and equipment between a construction project implementation group and suppliers, and formulates an efficient loading and unloading plan. The technology described in Patent Document 1 can reduce the loading and unloading costs and labor costs related to procurement of construction materials and equipment, and can improve the efficiency of loading and unloading work. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2003-132251 A Summary of the Invention [Problem to be solved by the invention]

[0006] Meanwhile, construction businesses are required to handle not only administrative tasks related to suppliers involved in the transactions of construction materials and equipment, but also administrative tasks related to the exchange between customers and work sites with businesses regarding various construction-related tasks and inspection tasks necessary for compliance with laws and regulations, such as asbestos inspections. The technology of Patent Document 1 can only reduce the costs of carrying in and out construction materials and labor costs, and improve the efficiency of carrying in and out tasks. Therefore, there is room for further improvement in the technology described in Patent Document 1 in terms of providing one-stop support for the overall handling of construction business business agents' administrative tasks, including coordination between customers and work sites with businesses, regarding various tasks, including tasks that reflect the unique circumstances of construction businesses, such as inspections necessary for compliance with laws and regulations.

[0007] The present invention has been made in consideration of the above circumstances. The object of the present invention is to support the performance of administrative tasks on behalf of construction companies, including coordination between clients, work sites, and companies, for various tasks, including tasks that reflect the unique circumstances of construction companies, such as inspections required for compliance with laws and regulations. [Means for solving the problem]

[0008] As a result of intensive research into solving the above problems, the inventors have found that the above object can be achieved by centrally managing communication records, transaction information, and work schedules including asbestos inspections, and performing one-stop operations such as generating materials to be used in creating transaction documents and registering work schedules. The inventors have then completed the present invention. Specifically, the present invention provides the following:

[0009] The present invention provides a support device for construction business agency, comprising a transaction information acquisition unit that acquires transaction information, which is information on a transaction related to a construction business, a communication record acquisition unit that acquires communication records between a construction business agency that acts on behalf of the construction business and the parties involved in the transaction, a data management unit that manages data associating the communication records with the transaction information, an inspection request command unit that commands the requesting of an inspection necessary for compliance with laws and regulations related to the transaction, a work schedule registration unit that registers a work schedule related to the transaction based on the data, and a material generation unit that generates materials to be used in creating transaction documents related to the construction business based on the data, wherein the parties involved in the transaction include the construction business, the workers related to the transaction, and the client related to the transaction, the work schedule registration unit registers the work schedule including the inspection, and the material generation unit is capable of generating materials including the communication records associated with the transaction and / or the work schedule associated with the transaction.

[0010] In the present invention, by managing the transaction information acquired by the transaction information acquisition unit and the communication records related to the construction company, the worker, and the client acquired by the communication record acquisition unit in the data management unit, materials including communication records and work schedules related to the transaction can be generated and used for creating transaction documents. In other words, the present invention contributes to the realization of a lean system and operation in which mutual feedback between the system and the user is realized.

[0011] However, circumstances unique to the construction industry include the requirement to carry out inspections necessary for compliance with laws and regulations, such as asbestos inspections, which are difficult for construction companies to carry out themselves. The present invention uses an inspection request command center to centrally manage various tasks, including such inspections, and compiles them into documents linked to communication records and work schedules related to construction companies, workers, and clients. Thus, the present invention supports the delegation of various administrative tasks related to construction companies, allowing construction companies to focus on their core tasks. Effect of the Invention

[0012] The present invention can assist construction companies in performing administrative tasks on their behalf, including coordination between clients, work sites, and companies, for various types of work, including work that reflects the specific circumstances of construction companies, such as inspections required for compliance with laws and regulations. [Brief description of the drawings]

[0013] [Figure 1] FIG. 1 is a block diagram showing an example of the hardware configuration and software configuration of a system S of the present embodiment. [Diagram 2] FIG. 2 is an example of data stored in the construction business operator database 121. [Diagram 3] FIG. 3 is a main flowchart showing an example of a preferable flow of the support process executed by the support device 1 of this embodiment. [Figure 4] FIG. 4 is a continuation of FIG. [Diagram 5] FIG. 5 is a continuation of FIG. [Figure 6] FIG. 6 is a continuation of FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] Hereinafter, an example of an embodiment of the present invention will be described in detail with reference to the drawings.

[0015] <System S> FIG. 1 is a block diagram showing an example of the hardware configuration and software configuration of the system S of this embodiment. An example of a preferred embodiment of the system S of this embodiment will be described below with reference to FIG. 1. The system S of this embodiment includes a construction business office work agent support device 1 that supports a construction business office work agent who performs the work of a construction business operator. Hereinafter, the construction business office work agent will also be simply referred to as an "agent." The support device 1 is capable of communicating with a terminal T via a network N.

[0016] [Support device 1] The support device 1 realizes each software component shown in Fig. 1 by using hardware components such as a control unit 11, a storage unit 12, and a communication unit 13. Then, the support device 1 executes a support process that supports the construction business operator in carrying out administrative work on behalf of the construction business operator by using each software component. The type of the support device 1 is not particularly limited. The type of the support device 1 may be, for example, various server devices, cloud servers, etc.

[0017] [Control unit 11] The control unit 11 includes a Central Processing Unit (CPU), a Random Access Memory (RAM), and a Read Only Memory (ROM).

[0018] The control unit 11 cooperates with the storage unit 12 and / or the communication unit 13 as necessary. The control unit 11 realizes software components of the program of this embodiment executed by the support device 1, such as a data management unit 111, a transaction information acquisition unit 112, a communication record acquisition unit 113, a customer schedule registration unit 114, an inspection request command unit 115, a work schedule registration unit 116, a document generation unit 117, and a billing agency request unit 118.

[0019] [Storage section 12] The memory unit 12 is a device in which data and / or files are stored, and includes a storage unit that stores data non-temporarily using a hard disk, a semiconductor memory, a recording medium, a memory card, and the like.

[0020] The storage unit 12 stores a program executed by the microcomputer, a construction company database 121, a list of inspections required for compliance with laws and regulations at construction companies, etc. In order to enable generation of a draft or the like using a large-scale language model, it is preferable that the storage unit 12 further stores a large-scale language model that has undergone a predetermined pre-learning. The pre-learning corresponding to each procedure such as generation of a draft will be described later together with each procedure using the large-scale language model.

[0021] (Construction Business Database 121) In the construction business operator database 121, construction business operator information, which is various data related to construction businesses, is stored in association with information identifying the construction business operator. The "information identifying the construction business operator" is, for example, a "construction business operator ID." The "various data related to construction businesses" includes at least "transaction information," which is information on transactions related to construction businesses, "communication records," and "schedules." In order to be utilized in generating various drafts, the "various data related to construction businesses" preferably includes basic information related to construction businesses.

[0022] "Basic information" includes various basic information of the construction company, such as the name of the construction company, the location of the business, contact information, business details, and each person in charge. There is no particular limitation on the contact information. For example, the contact information may be a telephone number, an email address, a URL for a contact form, a postal address, etc.

[0023] The "transaction information" includes data on various documents related to the transaction, such as proposals, estimates, purchase orders, schedules, schedules, and invoices. In order to support the construction business agent in creating documents, it is preferable that the "transaction information" further includes drafts of these various documents. These drafts are generated, for example, by the support device 1 of this embodiment.

[0024] "Communication records" include records of communication between a construction business agent and the parties involved in the transaction. "Parties involved in the transaction" include, for example, the construction business operator, the workers involved in the transaction, and the client (customer) involved in the transaction. The content of "communication records" is not particularly limited. The content of "communication records" includes, for example, the timing of making and receiving voice and video calls, such as telephone calls, the content of voice and video calls, the timing of sending and receiving text communications, such as emails, contact forms, and mail, and the content of text communications.

[0025] The "schedule" includes various schedules such as work schedules related to construction businesses. The "schedule" includes at least schedules related to requests for inspections required for compliance with laws and regulations. In order to ensure that customer schedules are not overlooked, it is preferable that the "schedule" includes customer schedules, which are the schedules of customers involved in transactions.

[0026] 2 is an example of data stored in the construction contractor database 121. In this example, the data stored includes first construction contractor information associated with a construction contractor ID "C0001", second construction contractor information associated with a construction contractor ID "C0002", and the like.

[0027] The first construction business information includes basic information such as the name "△△ Construction Co., Ltd.", business address "△-△, △△ Ward, △△ City, △△ Prefecture," contact information "(TEL) △△△ (△△△) △△△△ (E-Mail) foo@foo.foo.bar," transaction information such as draft proposal 1, proposal 1, draft schedule 1, schedule 1, draft estimate 1, estimate 1, draft purchase order 1, purchase order 1, invoice 1, communication records such as "△△ month △△ day △△: △△ phone call from △△, content: ··· △△ month △△ day △△: △△ email to △△, content: ···," and schedules such as "△△ month △△ day △△: △△ at site △△, asbestos inspection commissioned to △△ Company, client △△ present."

[0028] The second construction business information includes basic information such as the name "△△ Gumi Co., Ltd.", business address "△-△, △△ town, △△ city, △△ prefecture," contact information "(TEL) △△△ (△△△) △△△△ (E-Mail) bar@bar.foo.bar," transaction information such as draft proposal 2, proposal 2, draft schedule 2, schedule 2, draft estimate 2, estimate 2, draft purchase order 2, purchase order 2, invoice 2, communication records such as "△△ month △△ day △△: △△ Video call with △△, content: ··· Data: (video data 1)," and schedules such as "△△ month △△ day △△: △△ to site △△, scheduled to attend: client △△, site supervisor △△, worker △ names."

[0029] By storing various data related to construction businesses such as the first construction business information and the second construction business information in this example, the support device 1 can generate materials including communication records and work schedules related to the transaction, and can utilize them in creating transaction documents. In addition, the support device 1 can centrally manage various tasks including asbestos inspections related to the first construction business information, and compile them into materials associated with communication records and work schedules related to the construction business, the person in charge of work, and the client.

[0030] [Communications Section 13] The communication unit 13 is not particularly limited as long as it can connect the support device 1 to the network N and communicate with the terminal T, etc. An example of the communication unit 13 is a network card compatible with the Ethernet standard.

[0031] [Network N] The type of the network N is not particularly limited as long as it enables communication between the support device 1 and the terminal T. The type of the network N is, for example, the Internet, a mobile phone network, a wireless LAN, or the like.

[0032] [Terminal T] There is no particular limitation on the type of the terminal T. The terminal T may be, for example, a personal computer, a laptop computer, a smartphone, a tablet terminal, or the like.

[0033] [Main Flowchart of Support Processing] Fig. 3 is a main flow chart showing an example of a preferable flow of the support processing executed by the support device 1 of this embodiment. Fig. 4 is a diagram continuing from Fig. 3. Fig. 5 is a diagram continuing from Fig. 4. Fig. 6 is a diagram continuing from Fig. 5. An example of a preferable flow of the support processing executed by the support device 1 of this embodiment will be described below with reference to Figs. 3 to 6.

[0034] First, the support device 1 executes a series of processes related to the data registration of the construction business operator as a part of the support process. Steps S1 to S2 are an example of the process. This allows the support device 1 to centrally manage data on various tasks related to the execution of administrative tasks on behalf of the construction business operator in association with the registered data.

[0035] [Step S1: Determine whether to register construction company data] The control unit 11 executes the data management unit 111 in cooperation with the storage unit 12 and the communication unit 13. Then, the control unit 11 executes a process of determining whether or not to register the data of the construction business operator through the data management unit 111 (data registration determination step). If it is determined that the data should be registered, the control unit 11 shifts the process to step S2. If it is determined that the data should not be registered, the control unit 11 shifts the process to step S3.

[0036] The procedure for determining whether to register the data of the construction company is not particularly limited. For example, the procedure includes a procedure for determining that the data of the construction company is to be registered when a command to register data is received from the terminal T or the like.

[0037] [Step S2: Register construction company data] The control unit 11 executes a process of registering the data of the construction contractor determined to be registered in the data registration determination step in the construction contractor database 121 or the like by the data management unit 111 (data registration step). The control unit 11 shifts the process to step S3.

[0038] The data to be registered in the data registration step is not particularly limited. In order to reflect basic information in the materials, the data preferably includes basic information of the construction business operator. In order to reflect past communications and transactions in the materials, the data preferably further includes past communication records, transaction information, etc. related to the construction business operator.

[0039] The support device 1 executes a series of processes related to acquiring transaction information as a part of the support process. Steps S3 to S4 are an example of the process. This allows the support device 1 to generate materials that reflect the transaction information.

[0040] [Step S3: Determine whether to acquire transaction information] The control unit 11 executes the transaction information acquisition unit 112 in cooperation with the storage unit 12 and the communication unit 13. Then, the control unit 11 executes a process of determining whether to acquire transaction information, which is information on a transaction related to a construction business operator, by the transaction information acquisition unit 112 (transaction information acquisition determination step). If it is determined that the transaction information is to be acquired, the control unit 11 shifts the process to step S4. If it is not determined that the transaction information is to be acquired, the control unit 11 shifts the process to step S5. The procedure of determining whether to acquire the transaction information is not particularly limited. The procedure includes, for example, a procedure of determining that the transaction information is to be acquired when the transaction information is received from a terminal T or the like.

[0041] [Step S4: Obtain transaction information] The control unit 11 executes a process of acquiring the transaction information determined to be acquired in the transaction information acquisition determination step by the transaction information acquisition unit 112, and registering the transaction information in the construction business operator database 121, etc. (transaction information acquisition step). The control unit 11 shifts the process to step S5.

[0042] The transaction information acquired in the transaction information acquisition step is not particularly limited. In order to reflect various documents in the materials, the transaction information preferably includes data on various documents related to the transaction, such as a proposal, an estimate, a purchase order, a schedule, and an invoice.

[0043] The support device 1 executes a series of processes related to acquiring the communication records as a part of the support process. Steps S5 to S6 are an example of the process. This allows the support device 1 to generate materials that reflect the communication records.

[0044] [Step S5: Determine whether to obtain communication records] The control unit 11 executes the communication record acquisition unit 113 in cooperation with the memory unit 12 and the communication unit 13. The control unit 11 then executes a process of determining whether to acquire a communication record, which is information on a transaction related to a construction business operator, by the communication record acquisition unit 113 (communication record acquisition determination step). If it is determined that the communication record should be acquired, the control unit 11 transfers the process to step S6. If it is determined that the communication record should not be acquired, the control unit 11 transfers the process to step S7. The procedure for determining whether to acquire the communication record is not particularly limited. The procedure includes, for example, a procedure of determining that the communication record should be acquired when the communication record is received from terminal T or the like.

[0045] [Step S6: Obtain communication records] The control unit 11 executes a process of acquiring the communication records determined to be acquired in the communication record acquisition determination step by the communication record acquisition unit 113, and registering the communication records in the construction business operator database 121 or the like (communication record acquisition step). The control unit 11 shifts the process to step S7.

[0046] The communication records acquired in the communication record acquisition step are not particularly limited. In order to include communication records between the construction business office agent and various parties involved in the transaction, it is preferable that the parties involved in the transaction in the communication records include the construction business operator, the workers involved in the transaction, and the client (customer) involved in the transaction. The contents of the communication records are not particularly limited, and include, for example, the timing of making and receiving voice and video calls, such as telephone calls, the contents of voice and video calls, the timing of sending and receiving text communications, such as emails and contact forms, and the contents of text communications.

[0047] [Steps for providing communication records] In order to support the agent's response using past communication records, the support device 1 preferably executes a communication record providing step of providing the stored communication records to the agent as a part of the support process. The communication record providing step includes, for example, a procedure of searching for communication records stored in the construction business operator database 121 in response to an instruction from the agent and displaying the results on the terminal T or the like.

[0048] As a part of the support process, the support device 1 preferably executes a series of processes related to the registration of a customer schedule. Due to circumstances specific to a construction company, a schedule that requires coordination with a customer, such as a site inspection, may occur. Through the above-mentioned series of processes, the support device 1 can manage the customer schedule, generate materials that reflect the customer schedule, and support such coordination. Steps S7 to S8 are an example of this process.

[0049] [Step S7: Determine whether to register a customer schedule] The control unit 11 cooperates with the storage unit 12 and the communication unit 13 to execute the customer schedule registration unit 114. Then, the control unit 11 executes a process to determine whether or not to register a customer schedule, which is the schedule of the customer related to the above-mentioned transaction, through the customer schedule registration unit 114 (customer schedule registration determination step). If it is determined that registration should be performed, the control unit 11 shifts the process to step S8. If it is determined that registration should not be performed, the control unit 11 shifts the process to step S9.

[0050] The procedure for determining whether to register a customer schedule is not particularly limited. The procedure includes, for example, a procedure for determining that a customer schedule should be registered when a command to register a customer schedule is received from terminal T, etc. The procedure also includes, for example, a procedure for determining that a customer schedule should be registered when an analysis result is obtained indicating that the communication records and / or transaction information acquired and registered in the above-mentioned process include a customer schedule.

[0051] The analysis is realized by natural language processing using, for example, a large-scale language model, a voice recognition network, etc. When realized by a large-scale language model, the large-scale language model is preferably pre-trained for a process of extracting a customer schedule from text data using training data with text data as an explanatory variable and a customer schedule as a target variable. When realized by a voice recognition network, the voice recognition network is preferably pre-trained for a process of extracting a customer schedule from call data using training data with call data as an explanatory variable and a customer schedule as a target variable.

[0052] [Step S8: Register customer schedule] The control unit 11 executes a process of registering the customer schedule determined to be registered in the customer schedule registration determination step in the construction business operator database 121 or the like by the communication record acquisition unit 113 (customer schedule registration step). The control unit 11 shifts the process to step S9.

[0053] The customer schedule acquired in the customer schedule registration step is not particularly limited. In order to support the proxy of administrative work related to inspections that are necessary for compliance with laws and regulations and are difficult for construction businesses to carry out themselves, the customer schedule preferably includes customer schedules related to inspections (such as asbestos inspections) necessary for compliance with laws and regulations related to the transaction, which will be described later.

[0054] As part of the support process, the support device 1 executes a series of processes related to issuing an inspection request command. Steps S9 to S10 are an example of such processes. Circumstances specific to the construction industry include the requirement for inspections that are necessary for compliance with laws and regulations, such as inspections for asbestos, but that are difficult for construction businesses to carry out themselves. The series of processes related to the inspection request command unit 115 centrally manages various tasks, including such inspections, and can compile them into documents linked to communication records and work schedules related to construction businesses, workers, and clients.

[0055] [Step S9: Determine whether to issue an inspection request] The control unit 11 executes the inspection request command unit 115 in cooperation with the storage unit 12 and the communication unit 13. Then, the control unit 11 executes a process of determining whether to issue an inspection request required for compliance with laws and regulations related to the above-mentioned transaction by the inspection request command unit 115 (inspection request command determination step). If it is determined that an inspection request should be issued, the control unit 11 shifts the process to step S10. If it is not determined that an inspection request should be issued, the control unit 11 shifts the process to step S11.

[0056] The procedure for determining whether to issue an inspection request is not particularly limited. For example, the procedure includes a procedure for determining to register a customer schedule when an analysis result indicating that an inspection is required is obtained from the communication records and / or transaction information acquired and registered in the above-mentioned process.

[0057] The analysis is realized by natural language processing using, for example, a large-scale language model, a voice recognition network, etc. When realized by a large-scale language model, it is preferable that the large-scale language model has been pre-trained for a process of determining the necessity and type of an examination from text data using training data with text data as explanatory variables and the necessity and type of an examination as objective variables. When realized by a voice recognition network, it is preferable that the voice recognition network has been pre-trained for a process of determining the necessity and type of an examination from call data using training data with call data as explanatory variables and the necessity and type of an examination as objective variables.

[0058] [Step S10: Issue an inspection request] The control unit 11 executes a process of issuing an inspection request determined to be issued in the inspection request command determination step to the terminal T, etc., by the inspection request command unit 115 (inspection request command step). The control unit 11 moves the process to step S11. That is, the inspection request command step issues a command to request an inspection for asbestos, etc., to an inspection company different from the above-mentioned construction company.

[0059] The inspection request command step includes, for example, a procedure for displaying a notice related to the inspection request, a draft of a document related to the inspection request, etc. on the terminal T or the like. The document related to the inspection request is, for example, a form to be sent to an inspection agency. This allows the support device 1 to command the inspection request to an agent who performs administrative tasks on behalf of the construction business operator via the terminal T or the like used by the agent. An example of an inspection that is necessary for compliance with laws and regulations but is difficult for the construction business operator to perform by itself is an asbestos inspection.

[0060] In order to enable review of past administrative work related to the inspection request, the inspection request command step preferably includes a procedure for storing the history related to the inspection request in the storage unit 12. In order to make the costs related to the inspection request clear at a glance, the inspection request command step preferably includes a procedure for displaying a list of the costs, etc. related to the inspection request. In order to support applications for inspection, exemplified by applications using G Biz, etc., the inspection request command step preferably includes a procedure for making an application for inspection.

[0061] The support device 1 executes a series of processes related to the registration of a work schedule as a part of the support process. Steps S11 to S12 are an example of the process. This allows the support device 1 to share the progress in a timely manner among the people involved. This also allows the support device 1 to generate materials that reflect the work schedule.

[0062] [Step S11: Determine whether to register a work schedule] The control unit 11 executes the work schedule registration unit 116 in cooperation with the storage unit 12 and the communication unit 13. Then, the control unit 11 executes a process of determining whether to register a work schedule related to the above-mentioned transaction using the work schedule registration unit 116 (a work schedule registration determination step). If it is determined that the work schedule should be registered, the control unit 11 shifts the process to step S12. If it is determined that the work schedule should not be registered, the control unit 11 shifts the process to step S13.

[0063] The procedure for determining whether to register a work schedule is not particularly limited. For example, the procedure includes a procedure for determining that a work schedule is to be registered when a command to register a work schedule is received from the terminal T, etc. Also, the procedure includes a procedure for determining that a work schedule is to be registered when, for example, an analysis result including a work schedule for the transaction related thereto is obtained by analyzing the communication record and / or transaction information acquired and registered in the above-mentioned process.

[0064] The analysis is realized by natural language processing using, for example, a large-scale language model, a voice recognition network, etc. When realized by a large-scale language model, the large-scale language model is preferably pre-trained for a process of determining a work schedule from text data using training data with text data as an explanatory variable and a work schedule as a target variable. When realized by a voice recognition network, the voice recognition network is preferably pre-trained for a process of determining a work schedule from call data using training data with call data as an explanatory variable and a work schedule as a target variable.

[0065] [Step S12: Register work schedule] The control unit 11 executes a process of registering the work schedule determined to be instructed in the work schedule registration determination step in the construction business operator database 121 or the like by the work schedule registration unit 116 (work schedule registration step). The control unit 11 shifts the process to step S13.

[0066] The work schedule acquired in the work schedule registration step is not particularly limited. In order to support the delegation of administrative work related to inspections necessary for legal compliance that are difficult for construction businesses to carry out themselves, it is preferable that the work schedule includes a work schedule related to inspections necessary for legal compliance related to the transaction (such as asbestos inspections).

[0067] [Notification Step] As a part of the support process, the support device 1 preferably executes a notification step of notifying the customer schedule registered in the customer schedule registration step and / or the work schedule registered in the work schedule registration step. The notification means in the notification step is, for example, email, instant messenger, short message, etc.

[0068] As part of the support process, the support device 1 executes a series of processes for generating materials to be used in creating transaction documents related to construction businesses. When acting on behalf of construction businesses, it can be difficult to appropriately use technical terms and phrases specific to the construction industry. Through this series of processes, the support device 1 can achieve highly accurate collaboration between the agent and the relevant parties, and quick response. In addition, through this series of processes, the support device 1 can generate materials including communication records and work schedules related to transactions, and support the appropriate use of technical terms and phrases specific to the construction industry.

[0069] Steps S13 to S14 are an example of the process for generating a draft of an invoice. The support device 1 of the present embodiment can also generate drafts of other transaction documents, such as proposals, quotations, purchase orders, schedules, and timetables, in a similar manner.

[0070] [Step S13: Determine whether to generate a draft invoice] The control unit 11 executes the material generation unit 117 in cooperation with the storage unit 12 and the communication unit 13. The control unit 11 then executes a process of determining whether or not to generate materials such as a draft of a transaction document related to the above-mentioned transaction (e.g., a draft of an invoice, etc.) using the material generation unit 117 (material generation determination step). If it is determined that such materials should be generated, the control unit 11 shifts the process to step S14. If it is determined that such materials should not be generated, the control unit 11 shifts the process to step S15.

[0071] The procedure for determining whether to generate the document is not particularly limited. For example, the procedure includes a procedure for determining to generate the document when a command to generate the document is received from the terminal T, etc. Also, the procedure includes a procedure for determining to generate the document when an analysis result is obtained indicating that a transaction document related thereto is required, based on the analysis of the communication records and / or transaction information acquired and registered in the above-mentioned process.

[0072] The analysis is realized, for example, by natural language processing using a large-scale language model, a voice recognition network, etc. When realized by a large-scale language model, the large-scale language model is preferably pre-trained for a process of determining whether or not a transaction document is required from text data using training data with text data as an explanatory variable and whether or not a transaction document is required as an objective variable. When realized by a voice recognition network, the voice recognition network is preferably pre-trained for a process of determining whether or not a transaction document is required from call data using training data with call data as an explanatory variable and whether or not a transaction document is required as an objective variable.

[0073] [Step S14: Generate a draft invoice] The control unit 11 executes a process of generating materials (e.g., a draft of an invoice, etc.) of the transaction document determined to be instructed in the material generation determination step by the material generation unit 117 (material generation step). The control unit 11 shifts the process to step S15.

[0074] The procedure for generating the materials in the material generating step is not particularly limited. For example, the procedure includes a procedure for acquiring past transaction documents stored in the storage unit 12. In addition, in order to generate materials including appropriate language expressions, the procedure preferably includes a procedure for generating the materials by natural language processing using a large-scale language model.

[0075] At this time, in order to generate materials according to the type of transaction document, it is preferable that the large-scale language model has been pre-trained on a process for generating the content of materials according to the type of transaction document using training data in which the type of transaction document is used as an explanatory variable and the content of materials according to that type of transaction document is used as an objective variable.

[0076] In addition, at this time, in order to generate materials appropriate for each construction company, it is preferable that the large-scale language model has been pre-trained for a process of generating the content of materials appropriate for each construction company, etc., using training data that further includes information identifying the construction company as an explanatory variable.

[0077] Furthermore, at this time, in order to generate materials according to the type of material, it is preferable that the large-scale language model further includes the type of material as an explanatory variable, and that pre-training has been performed on a process of generating the contents of materials according to the type of material, etc., using training data including materials according to the type of material, etc., as a target variable.

[0078] [Transaction document history storage step] In order to enable review of past administrative work related to the creation of the transaction document, the support process preferably includes a transaction document history storage step of storing a history related to the creation of the transaction document in the memory unit 12. The history includes materials created in the material generation step, transaction documents created based on the materials, etc. In order to enable determination of the chronological order of the administrative work, the history is preferably associated with the timing of storage. The history in the transaction document history storage step is stored in, for example, the construction business operator database 121.

[0079] In order to reflect various data stored in the storage unit 12, such as basic information, transaction information, communication records, customer schedules, inspection requests, work schedules, etc., the document generation step preferably includes a procedure of referring to various data stored in the storage unit 12. The reference is realized, for example, by executing a procedure of providing the various data stored in the storage unit 12 as input to a large-scale language model, or by adding a module that refers to the construction business operator database 121 from the large-scale language model to the large-scale language model.

[0080] In this case, it is preferable that the large-scale language model includes, as explanatory variables, at least one of the various data stored in the memory unit 12, such as basic information, transaction information, communication records, customer schedules, inspection requests, and work schedules, and the type of document, and that pre-training has been performed on a process of generating the content of the document according to the type of document and various data, using training data in which the content of the document of the type reflecting the data is the objective variable.

[0081] As a part of the support process, the support device 1 preferably executes a series of processes related to a proxy request for billing. Steps S15 to S16 are an example of such processes. This allows the support device 1 to support a proxy request for billing related to the above-mentioned transaction.

[0082] [Step S15: Determine whether to request proxy billing] The control unit 11 cooperates with the storage unit 12 and the communication unit 13 to execute the billing agency request unit 118. Then, the control unit 11 executes a process of determining whether to request agency billing for the above-mentioned transaction through the billing agency request unit 118 (billing agency request determination step). If it is determined that a request should be made, the control unit 11 moves the process to step S16. If it is determined that a request should not be made, the control unit 11 returns the process to step S1, and repeats the processes from step S1 to step S16.

[0083] The procedure for determining whether to request proxy billing is not particularly limited. The procedure includes, for example, a procedure for determining that proxy billing is to be requested when a proxy billing request is instructed from the terminal T or the like.

[0084] [Step S16: Request for billing] The control unit 11 executes a process of requesting the billing agency to act on behalf of the billing based on the billing amount of the bill related to the above-mentioned transaction through the billing agency request unit 118 (billing agency request step). The control unit 11 returns the process to step S1 and repeats the processes from step S1 to step S16. The billing agency request step includes a procedure of instructing a server of a billing agency, exemplified by various settlement services, etc., to act on behalf of the billing based on the billing amount.

[0085] [Daily report generation step] In order to support communication between the agent and the construction company through the daily report, the support device 1 preferably executes a daily report generation step of generating periodic reports as part of the support process. The daily report generation step includes, for example, a procedure of generating a daily report in response to an instruction from the agent, storing the report in the construction company database 121, and transmitting the report to a terminal T or the like used by the construction company.

[0086] The daily report generating step is not limited to generating a daily report, but may be configured to generate various types of periodic reports, exemplified by weekly reports, monthly reports, semi-annual reports, etc. In addition, in order to support reporting of matters for which it is not appropriate to postpone reporting until the creation of a periodic report, the daily report generating step is preferably configured to generate an ad hoc report.

[0087] In order to reduce the burden of preparing formats for daily reports one by one, the daily report generation step preferably includes a procedure for generating a draft of the daily report by a procedure similar to that of the document generation step. In order to reflect the various data stored in the storage unit 12, the procedure preferably includes a procedure for referring to the various data stored in the storage unit 12, similar to that of the document generation step.

[0088] [Effects of Support Processing] By executing the above-mentioned support process, the support device 1 of this embodiment manages the transaction information acquired by the transaction information acquisition unit 112 and the communication records related to the construction company, the worker, and the client acquired by the communication record acquisition unit 113 in the data management unit 111. Then, the material generation unit 117 of the support device 1 uses the data managed by the data management unit 111 to generate materials including communication records and work schedules related to the transaction, and can be used to create transaction documents.

[0089] Meanwhile, circumstances unique to the construction industry include the requirement to carry out inspections necessary for compliance with laws and regulations, such as inspections for asbestos, which are difficult for construction companies to carry out themselves. The support device 1 of this embodiment can centrally manage various tasks, including such inspections, using the inspection request command unit 115, and compile them into documents linked to communication records and work schedules related to construction companies, workers, and clients. Thus, the support device 1 of this embodiment can support the delegation of various administrative tasks related to construction companies, allowing construction companies to focus on their core tasks.

[0090] In addition, the inspection request command unit 115 of the support device 1 of this embodiment can take a form in which it commands the construction company to request an asbestos inspection to an inspection company other than the construction company. This form can support the request for an asbestos inspection, which is an important inspection that is necessary for compliance with laws and regulations and is difficult for the construction company to carry out by itself, thereby supporting the execution of administrative work on behalf of the construction company in consideration of the unique circumstances of the construction industry.

[0091] In addition, the support device 1 of this embodiment may further include a customer schedule registration unit 114 that registers a customer schedule, which is the schedule of a customer related to a transaction, based on data managed by the data management unit 111, and the material generation unit 117 may generate materials including the customer schedule associated with the transaction. In this embodiment, by generating materials including the customer schedule associated with the transaction, the management of customer schedules can be included in the unified management of various tasks. As a result, the support device 1 of this embodiment can support the performance of administrative tasks in accordance with the unique circumstances of the construction industry, which require coordination between construction companies, workers, and clients.

[0092] Furthermore, the support device 1 of this embodiment may have a mode further including a billing agency request unit 118 that requests an agency to act on behalf of a billing related to a transaction. This mode can provide support for requesting an agency to act on behalf of a billing related to a transaction. At this time, the material generation unit 117 of the support device 1 may generate materials including a draft of the billing amount related to the transaction. This mode can provide comprehensive support for a series of procedures related to the agency of billing related to a transaction, from creating a draft to acting on behalf of the billing.

[0093] As described above, the support device 1 of this embodiment can support the administrative work of construction companies, including coordination between customers, work sites, and companies, for various tasks, including tasks that reflect the specific circumstances of construction companies, such as inspections required for compliance with laws and regulations.

[0094] <Example of use of support device 1> The following is an example of how the support device 1 of this embodiment is used.

[0095] [Register construction company data] An agent who performs administrative tasks on behalf of a construction company transmits data of the construction company to the support device 1 via a terminal T or the like. The support device 1 registers the data in the construction company database 121.

[0096] [Get transaction information] The agent receives various documents related to the transaction, such as proposals, estimates, purchase orders, schedules, invoices, etc., and transmits the transaction information, which is the data, to the support device 1 via a terminal T, etc. The support device 1 stores the transaction information in the construction business operator database 121. The agent creates various documents while appropriately referring to materials generated based on the stored transaction information, etc. Then, the agent transmits data of the created various documents to the support device 1 as transaction information. The support device 1 stores the data in the construction business operator database 121.

[0097] [Responses by phone, email, messenger, etc.] The agent responds to calls, emails, messages via instant messenger, mailed letters, etc., made to the construction business operator, and transmits communication records relating to these responses to the support device 1 via a terminal T or the like. The support device 1 stores the response records in the construction business operator database 121. In responding to such requests, the agent refers to the stored communication records as appropriate.

[0098] [Task registration] The agent transmits the above-mentioned various documents, work schedules, customer schedules, such as tasks related to responses, to the support device 1. The support device 1 stores the work schedules and customer schedules in the construction business operator database 121. The tasks are, for example, various tasks related to inspection requests necessary for compliance with laws and regulations, such as a request for an asbestos inspection.

[0099] [Request for proxy billing] The agent refers to the billing amount, the draft of the invoice, etc. provided by the support device 1 and makes a request to the billing agent to act on the behalf of the billing related to the invoice among the various documents mentioned above. The billing agent makes a bill to the billing destination such as a customer, and transfers the amount remaining after deducting a handling fee from the amount transferred by the billing destination to the agent or the construction business operator.

[0100] It should be noted that within the scope of the concept of the present invention, a person skilled in the art may come up with various modifications and alterations. It is understood that such modifications and alterations fall within the scope of the present invention. For example, even if a person skilled in the art appropriately adds, deletes, or modifies the design of the above-described embodiment, or adds, omits, or modifies the conditions of a process, these modifications and alterations are included in the scope of the present invention as long as they include the gist of the present invention. [Explanation of symbols]

[0101] S System 1 Support equipment 11 Control section 111 Data Management Department 112 Transaction Information Acquisition Department 113 Communication Record Acquisition Department 114 Customer Schedule Registration Department 115 Inspection Request Command 116 Work Schedule Registration Department 117 Material generation department 118 Billing Agency Request Department 12 Storage section 121 Construction Business Database 13. Communications Department N Network T-Terminal

Claims

1. A transaction information acquisition unit that acquires transaction information that is information on transactions related to construction businesses; a communication record acquisition unit that acquires communication records between a construction business agent who acts on behalf of the construction business operator and the parties involved in the transaction; a data management unit that manages data that associates the communication record with the transaction information; an inspection request command unit that commands the requesting of an inspection necessary for compliance with laws and regulations related to the transaction and displays a notice related to the inspection request on a terminal; a work schedule registration unit that registers a work schedule related to the transaction based on the data; a material generation unit that generates materials to be used in creating transaction documents related to the construction company based on the data; Equipped with A customer schedule is registered based on the data, which is a schedule of a customer related to the transaction. A registration unit is further provided, The parties in the transaction include the construction business operator, the workers in charge of the transaction, and the client in the transaction; The work schedule registration unit registers a work schedule including the inspection, The material generation unit generates materials including the communication record associated with the transaction and / or the work schedule associated with the transaction; The material generation unit generates a material including the customer schedule associated with the transaction; the inspection request command unit issues a command to request the inspection when an analysis result indicating that an inspection is required is obtained by analyzing the communication record and / or the transaction information through natural language processing using a large-scale language model that has been pre-trained using training data with text data as an explanatory variable and the necessity and type of inspection as an objective variable, and a voice recognition network that has been pre-trained using training data with call data as an explanatory variable and the necessity and type of inspection as an objective variable; Support device for construction industry administrative agency.

2. The inspection request command unit is to request an inspection of asbestos from an inspection company other than the construction company. The support device according to claim 1 , further comprising:

3. A billing agency request unit is further provided for requesting a billing agency to act on behalf of the billing related to the transaction, The transaction information includes an amount charged for the transaction; The billing agent request unit requests a billing agent based on the billing amount. The support device according to claim 1 .

4. The document generation unit generates documents including a draft of the billing amount for the transaction based on the data. The support device according to claim 3 .

Images