Support device for construction business proxy processing
The construction business office agent support device addresses administrative challenges by centrally managing communication and transaction data to generate documents and schedules, enabling efficient task management and legal compliance support.
Patent Information
- Application Number
- JP2024020408
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-02-14
- Publication Date
- 2025-08-26
- Estimated Expiration
- 2044-02-14
AI Technical Summary
Construction companies face challenges in managing administrative tasks such as customer support, data registration, and financial operations, including communication and operational costs, and need support for tasks like inspections required for legal compliance that are difficult to perform independently.
A construction business office agent support device that centrally manages communication records, transaction information, and work schedules, including inspections, to generate transaction documents and register work schedules, supporting coordination between clients, work sites, and companies.
The device assists construction companies in performing administrative tasks efficiently, focusing on core business by managing inspections and other tasks required for legal compliance, reducing operational burdens.
Smart Images

Figure 2025124393000001_ABST
Abstract
Description
[Technical Field]
[0001] The present invention relates to a construction business agency support device. [Background technology]
[0002] Construction companies want to reduce the burden of administrative tasks such as customer support, data registration, and financial operations, so that they can focus on their core business. 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 business, and flexibly respond to changes in business scale.
[0003] However, the introduction of BPO can present various hurdles, such as implementation costs, communication costs, and operational costs. Implementation costs include the time and financial costs associated with business process analysis, system integration, and staff training. Communication costs include the cost of communicating the details of a construction company's work to specialists. Operational costs include staff labor costs. Therefore, there is a demand for technology that can support construction companies in outsourcing their administrative work.
[0004] Regarding technology to support administrative work at construction companies, Patent Document 1 discloses a method for supporting construction material procurement in which a support center centrally manages transactions of construction materials between a construction project implementation group and suppliers, and formulates an efficient delivery plan. The technology described in Patent Document 1 can reduce delivery costs and labor costs related to the procurement of construction materials, and can improve the efficiency of delivery work. [Prior art documents] [Patent documents]
[0005] [Patent Document 1] Japanese Patent Application Laid-Open No. 2003-132251 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 trading of construction materials and equipment, but also administrative tasks related to communications between customers and work sites and businesses regarding various construction-related tasks and inspections required for compliance with laws and regulations, such as asbestos inspections. The technology disclosed in Patent Document 1 is only capable of reducing the costs of carrying in and out construction materials and labor costs, and improving 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 all administrative tasks on behalf of construction businesses, including coordination between customers and work sites and businesses, regarding various tasks, including tasks that reflect the unique circumstances of construction businesses, such as inspections required for compliance with laws and regulations.
[0007] The present invention has been made in consideration of the above circumstances. The purpose of the present invention is to support the administrative work of construction companies, including coordination between clients, work sites, and companies, for various types of work, including work that reflects the unique circumstances of construction companies, such as inspections required for legal compliance. [Means for solving the problem]
[0008] As a result of intensive research into solving the above-mentioned problems, the inventors have discovered that the above-mentioned object can be achieved by centrally managing communication records, transaction information, and work schedules including asbestos inspections, and by performing the creation of materials to be used in creating transaction documents and the registration of work schedules in one stop.The inventors have then completed the present invention.Specifically, the present invention provides the following.
[0009] The present invention provides a construction business office agent support device comprising: a transaction information acquisition unit that acquires transaction information, which is information on transactions related to construction businesses; a communication record acquisition unit that acquires communication records between a construction business office agent who acts on behalf of the construction business's affairs and the parties involved in the transaction; a data management unit that manages data that associates the communication records with the transaction information; an inspection request command unit that commands the requesting of inspections 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 based on the data to be used in creating transaction documents related to the construction business, wherein the parties involved in the transaction include the construction business, the work personnel related to the transaction, and the client related to the transaction, and 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] The present invention allows a data management unit to manage transaction information acquired by a transaction information acquisition unit and communication records relating to construction companies, workers, and clients acquired by a communication record acquisition unit, thereby generating materials including communication records and work schedules related to transactions and utilizing them in 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 users is realized.
[0011] However, circumstances unique to the construction industry include the need for inspections that are necessary for compliance with laws and regulations, such as asbestos inspections, but that are difficult for construction companies to conduct themselves. This invention centrally manages various tasks, including such inspections, through an inspection request command center, and compiles them into documents linked to communication records and work schedules related to construction companies, workers, and clients. Therefore, this invention supports the proxy handling of various administrative tasks related to construction companies, allowing construction companies to focus on their core business. [Effects of the Invention]
[0012] The present invention can assist construction companies in performing administrative tasks, including coordination between customers, 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 explanation of the drawings]
[0013] [Figure 1] FIG. 1 is a block diagram showing an example of the hardware and software configuration of a system S according to this embodiment. [Figure 2] FIG. 2 is an example of data stored in the construction company database 121. [Figure 3] FIG. 3 is a main flowchart showing an example of a preferable flow of the assistance process executed by the assistance device 1 of this embodiment. [Figure 4] FIG. 4 is a continuation of FIG. [Figure 5] FIG. 5 is a continuation of FIG. [Figure 6] FIG. 6 is a continuation of FIG. DETAILED DESCRIPTION OF THE INVENTION
[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 using FIG. 1. The system S of this embodiment is configured to include a construction business office work agent support device 1 that supports a construction business office agent who handles the administrative work of a construction company. Hereinafter, the construction business office 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 using hardware components such as a control unit 11, a storage unit 12, and a communication unit 13. The support device 1 then executes support processing to support the construction company in performing administrative tasks on its behalf 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), a read only memory (ROM), and the like.
[0018] The control unit 11 cooperates with the storage unit 12 and / or the communication unit 13 as necessary. The control unit 11 then realizes the 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 unit 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, or 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 construction companies to comply with laws and regulations, etc. In order to enable the generation of drafts, etc. using a large-scale language model, it is preferable that the storage unit 12 also stores a large-scale language model that has undergone predetermined pre-training. The pre-training corresponding to each step of generating a draft, etc. will be explained later together with each step using the large-scale language model.
[0021] (Construction Business Database 121) The construction company database 121 stores construction company information, which is various data related to construction companies, in association with information identifying the construction company. The "information identifying the construction company" is, for example, a "construction company ID." The "various data related to construction companies" includes at least "transaction information," which is information on transactions related to construction companies, "communication records," and "schedules." It is preferable that the "various data related to construction companies" include basic information related to construction companies so that it can be used to generate various drafts.
[0022] "Basic information" includes various basic information about the construction company, such as the name of the construction company, business location, contact information, business details, and each person in charge. There are no particular limitations on the contact information. Examples of contact information include a telephone number, email address, URL of a contact form, and postal address.
[0023] The "transaction information" includes data on various documents related to the transaction, such as proposals, estimates, purchase orders, schedules, timetables, and invoices. In order to support the construction business agent in creating documents, the "transaction information" preferably 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 communications between a construction business administrative 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 the sending and receiving of voice and video calls, such as by telephone, the content of voice and video calls, the timing of sending and receiving of text communications, such as by email, contact form, and mail, and the content of text communications.
[0025] "Schedules" include various schedules such as work schedules related to construction businesses. "Schedules" include at least schedules related to requests for inspections required for legal compliance. In order to ensure that customer schedules are not overlooked, "schedules" preferably include customer schedules, which are the schedules of customers involved in transactions.
[0026] 2 is an example of data stored in the construction company database 121. In this example, the data stored includes first construction company information associated with construction company ID "C0001," second construction company information associated with construction company ID "C0002," and the like.
[0027] The first construction business operator 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 operator 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 start groundbreaking ceremony at site △△, scheduled to attend: client △△, site supervisor △△, worker △ name."
[0029] By storing various data related to construction businesses, such as the first construction business information and 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 use these materials to create 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, work personnel, and client.
[0030] [Communications Section 13] The communication unit 13 is not particularly limited as long as it connects the support device 1 to the network N and enables communication 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 allows the support device 1 and the terminal T to communicate with each other. 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 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 flowchart 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. Below, an example of a preferable flow of the support processing executed by the support device 1 of this embodiment will be described 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 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 work on behalf of the construction business operator by associating them 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 to register the construction business operator data by 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 not determined that the data should 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 whether to register the data of the construction company 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, etc. (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 about the construction company. In order to reflect past communications and transactions in the materials, the data preferably further includes past communications records, transaction information, etc. related to the construction company.
[0039] As part of the support process, the support device 1 executes a series of processes related to acquiring transaction information. Steps S3 to S4 are an example of such processes. 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 transactions related to construction businesses, by the transaction information acquisition unit 112 (transaction information acquisition determination step). If it is determined that the transaction information should be acquired, the control unit 11 shifts the process to step S4. If it is not determined that the transaction information should be acquired, the control unit 11 shifts the process to step S5. The procedure for determining whether to acquire the transaction information is not particularly limited. The procedure includes, for example, a procedure of determining that the transaction information should 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 acquired 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] As part of the assistance process, the assistance device 1 executes a series of processes related to acquiring communication records. Steps S5 to S6 are an example of such processes. This allows the assistance device 1 to generate materials that reflect the communication records.
[0044] [Step S5: Determine whether to acquire 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. Then, the control unit 11 executes a process of determining whether to acquire a communication record, which is information about 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 moves the process to step S6. If it is not determined that the communication record should be acquired, the control unit 11 moves 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, etc. (communication record acquisition step). The control unit 11 moves 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 administrative agent and various parties involved in the transaction, the parties involved in the transaction in the communication records preferably include the construction business operator, the workers involved in the transaction, and the client (customer) involved in the transaction. The content of the communication records is not particularly limited, and may include, for example, the timing of 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 and contact forms, and the content of text communications.
[0047] [Providing communication records] In order to support the agent in responding to a call 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 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 part of the support process, the support device 1 preferably executes a series of processes related to registering customer schedules. Due to circumstances specific to construction companies, schedules that require coordination with the customer, such as on-site inspections, may arise. Through the above-described series of processes, the support device 1 can manage customer schedules, generate materials that reflect the customer schedules, 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 to register a customer schedule, which is the schedule of the customer related to the above-mentioned transaction, using the customer schedule registration unit 114 (customer schedule registration determination step). If it is determined that the customer schedule should be registered, the control unit 11 shifts the process to step S8. If it is not determined that the customer schedule should be registered, 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. This procedure includes, for example, a procedure for determining to register a customer schedule when a command to register a customer schedule is received from terminal T, etc. This procedure also includes, for example, a procedure for determining to register a customer schedule when an analysis result indicating that the communication records and / or transaction information acquired and registered in the above-mentioned process contain a customer schedule is obtained.
[0051] The analysis is realized by natural language processing using, for example, a large-scale language model, a speech 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 in which text data is an explanatory variable and the customer schedule is a target variable. When realized by a speech recognition network, the speech recognition network is preferably pre-trained for a process of extracting a customer schedule from call data using training data in which call data is an explanatory variable and the customer schedule is 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, etc. (customer schedule registration step) by the communication record acquisition unit 113. The control unit 11 moves 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 outsourcing of administrative work related to inspections that are necessary for legal compliance but are difficult for construction businesses to carry out themselves, the customer schedule preferably includes customer schedules related to inspections (such as asbestos inspections) that are necessary for legal compliance related to the transaction, as 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 this process. Circumstances specific to the construction industry include the requirement for inspections that are necessary for compliance with laws and regulations, such as asbestos inspections, but are difficult for construction companies to perform 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 companies, 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 necessary for compliance with laws and regulations related to the transaction described above using 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, and includes, for example, 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 speech recognition network, etc. When realized by a large-scale language model, it is preferable that the large-scale language model has been pre-trained to perform a process of determining the necessity and type of testing from text data using training data with text data as explanatory variables and the necessity and type of testing as objective variables.When realized by a speech recognition network, it is preferable that the speech recognition network has been pre-trained to perform a process of determining the necessity and type of testing from call data using training data with call data as explanatory variables and the necessity and type of testing as objective variables.
[0058] [Step S10: Issue an inspection request] The control unit 11 executes a process of issuing an inspection request, which is 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 company different from the above-mentioned construction company to inspect for asbestos, etc.
[0059] The inspection request command step includes, for example, a procedure for displaying a notice related to the inspection request, a draft document related to the inspection request, etc. on a 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 work on behalf of the construction company via a terminal T or the like used by the agent. An inspection that is necessary for compliance with laws and regulations but is difficult for the construction company to carry out itself is, for example, an asbestos inspection.
[0060] In order to enable review of past administrative work related to inspection requests, the inspection request command step preferably includes a procedure for storing the history of inspection requests in the storage unit 12. In order to make the costs related to inspection requests clear at a glance, the inspection request command step preferably includes a procedure for displaying a list of costs, etc. related to inspection requests. In order to support applications related to inspections, such as applications using G Biz, the inspection request command step preferably includes a procedure for making applications related to inspections.
[0061] As part of the support process, the support device 1 executes a series of processes related to the registration of a work schedule. Steps S11 to S12 are an example of such processes. This allows the support device 1 to share progress information in a timely manner among the parties 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 (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 not determined that the work schedule should 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. This procedure includes, for example, a procedure for determining that a work schedule should be registered when a command to register a work schedule is received from terminal T, etc. This procedure also includes, for example, a procedure for determining that a work schedule should be registered when, by analyzing the communication records and / or transaction information acquired and registered in the above-mentioned process, an analysis result including a work schedule for the transaction related thereto is obtained.
[0064] The analysis is realized by natural language processing using, for example, a large-scale language model, a speech 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 in which text data is an explanatory variable and the work schedule is a target variable. When realized by a speech recognition network, the speech recognition network is preferably pre-trained for a process of determining a work schedule from call data using training data in which call data is an explanatory variable and the work schedule is 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, etc., by the work schedule registration unit 116 (work schedule registration step). The control unit 11 proceeds to step S13.
[0066] The work schedule acquired in the work schedule registration step is not particularly limited. In order to support the outsourcing of administrative work related to inspections that are necessary for compliance with laws and regulations but are difficult for construction businesses to carry out themselves, the work schedule preferably includes work schedules related to inspections (such as asbestos inspections) that are necessary for compliance with laws and regulations related to the transaction.
[0067] [Notification Step] As part of the assistance process, the assistance 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 method 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 to generate materials to be used in creating transaction documents related to construction businesses. When acting as an agent for construction businesses, it can be difficult to properly 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, as well as quick responses. In addition, through this series of processes, the support device 1 can generate materials including communication records and work schedules related to the transaction, and can support the appropriate use of technical terms and phrases specific to the construction industry.
[0069] Steps S13 and S14 are an example of the process for generating a draft of an invoice. The support device 1 of this embodiment can also generate drafts of other transaction documents, such as proposals, estimates, 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. Then, the control unit 11 executes a process of determining whether to generate materials such as a draft of a transaction document related to the above-mentioned transaction (for example, a draft of an invoice) using the material generation unit 117 (material generation determination step). If it is determined that the materials should be generated, the control unit 11 shifts the process to step S14. If it is not determined that the materials should 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 terminal T, etc. Also, for example, the procedure includes a procedure for determining to generate the document when an analysis result indicating that a transaction document related to the communication record and / or transaction information acquired and registered in the above-mentioned process is obtained.
[0072] The analysis is realized by natural language processing using, for example, a large-scale language model, a speech 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 business document is necessary from text data using training data with text data as an explanatory variable and whether or not a business document is necessary as an objective variable. When realized by a speech recognition network, the speech recognition network is preferably pre-trained for a process of determining whether or not a business document is necessary from call data using training data with call data as an explanatory variable and whether or not a business document is necessary as an objective variable.
[0073] [Step S14: Generate a draft of the invoice] The control unit 11 executes a process of generating materials (e.g., a draft of an invoice, etc.) for 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 generation step is not particularly limited. The procedure includes, for example, a procedure for retrieving past transaction documents stored in the storage unit 12. In addition, in order to generate materials containing appropriate linguistic expressions, the procedure preferably includes a procedure for generating the materials by natural language processing using a large-scale language model.
[0075] In this case, 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 to perform a process of 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 a target variable.
[0076] In addition, at this time, in order to generate materials tailored to the construction company, it is preferable that the large-scale language model has been pre-trained for a process of generating the content of materials tailored to the construction company, etc., using training data that further includes information identifying the construction company as an explanatory variable.
[0077] Furthermore, 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 for generating the content 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 transaction documents, the support process preferably includes a transaction document history storage step of storing a history related to the creation of transaction documents 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 be able to determine the chronological order of 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 for referencing various data stored in the storage unit 12. The reference is realized, for example, by executing a procedure for providing the various data stored in the storage unit 12 as input to a large-scale language model, or by adding a module for referencing 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 in which the data is reflected is the target variable.
[0081] As part of the support process, the support device 1 preferably executes a series of processes related to a request for proxy billing. Steps S15 to S16 are an example of such processes. This allows the support device 1 to support a request for proxy billing for 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 transaction described above using 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 not determined that a request should 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. For example, the procedure includes a procedure for determining whether proxy billing is to be requested when a command to request proxy billing is received from terminal T or the like.
[0084] [Step S16: Request for billing] The control unit 11 executes a process of requesting a billing agent 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 agent, 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 daily reports, 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 generation step is not limited to generating a daily report, but may be configured to generate various 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 generation 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 in the same manner as the document generation step. In order to reflect the various data stored in the storage unit 12, the procedure preferably includes a procedure for referencing the various data stored in the storage unit 12, similar to the document generation step.
[0088] [Effect of support processing] By executing the above-described 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 business operator, worker, and 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 use the materials to create transaction documents.
[0089] However, circumstances unique to the construction industry include the need for inspections that are necessary for compliance with laws and regulations, such as asbestos inspections, but that are difficult for construction companies to perform themselves. The support device 1 of this embodiment centrally manages various tasks, including such inspections, using the inspection request command unit 115, and can compile documents linked to communication records and work schedules related to construction companies, workers, and clients. Thus, the support device 1 of this embodiment supports the performance of various administrative tasks related to construction companies, allowing construction companies to focus on their core tasks.
[0090] Furthermore, the inspection request command unit 115 of the support device 1 of this embodiment can take a form in which it commands an inspection company other than the construction company to request an asbestos inspection. This form can support the request for an asbestos inspection, which is an important inspection necessary for compliance with laws and regulations and is difficult for the construction company to conduct itself, thereby providing support for administrative work substitution that takes into account 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 document generation unit 117 may generate documents including the customer schedule associated with the transaction. In this embodiment, by generating documents 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 administrative work substitution taking into account 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 configuration further including a billing agency request unit 118 that requests an agency to act on behalf of a client in making a bill for a transaction. This configuration can provide support for requesting an agency to act on behalf of a client in making a bill for a transaction. In this case, the document generation unit 117 of the support device 1 may generate a document including a draft of the billing amount for the transaction. This configuration can comprehensively support a series of procedures related to acting on behalf of a client in making a bill for a transaction, from creating a draft to acting on behalf of a client in making a bill.
[0093] As described above, the support device 1 of this embodiment can support construction companies in performing administrative tasks, 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 work 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, and invoices, and transmits the transaction information, which is the data, to the support device 1 via a terminal T or the like. 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 created based on the stored transaction information, etc. Then, the agent transmits the data of the various documents created as transaction information to the support device 1. The support device 1 stores the data in the construction business operator database 121.
[0097] [Responding via phone, email, messenger, etc.] The agent responds to telephone calls, emails, messages via instant messenger, mailed correspondence, etc. from the construction company, and sends communication records relating to these responses to the support device 1 via a terminal T, etc. The support device 1 stores the response records in the construction company database 121. When responding, the agent refers to the stored communication records as appropriate.
[0098] [Task registration] The agent transmits the above-mentioned various documents, work schedules, and customer schedules, such as tasks related to customer service, 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 required for compliance with laws and regulations, such as a request for asbestos inspection.
[0099] [Request for proxy billing] The agent refers to the billing amount, draft invoice, etc. provided by the support device 1 and requests the billing agent to act on behalf of the agent in billing related to the invoice among the various documents mentioned above. The billing agent invoices the billing recipient, such as a customer, and transfers the amount transferred by the billing recipient minus a handling fee to the agent or construction company.
[0100] It should be noted that within the scope of the concept of the present invention, those skilled in the art may conceive of various modifications and alterations. Therefore, 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 components of the above-described embodiment, or adds, omits, or modifies the conditions of a process, such modifications are also included within the scope of the present invention as long as they maintain 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 Center 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; 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 The parties involved in the transaction include the construction business operator, the person in charge of work involved in the transaction, and the client involved in the transaction, the work schedule registration unit registers a work schedule including the inspection, the material generation unit generates a material including the communication record associated with the transaction and / or the work schedule associated with the transaction. Support device for construction industry administrative agency.
2. 2. The support device according to claim 1, wherein the inspection request command unit commands the construction company to request an inspection for asbestos from an inspection company different from the construction company.
3. a customer schedule registration unit that registers a customer schedule that is a schedule of the customer relating to the transaction based on the data; the material generation unit generates a material including the customer schedule associated with the transaction. The support device according to claim 1 .
4. A billing agent request unit is further provided for requesting a billing agent to act on behalf of the billing agent for the transaction, The transaction information includes a billing amount for the transaction; The billing agent request unit requests a billing agent based on the billing amount. The support device according to claim 1 .
5. The support device according to claim 4 , wherein the document generation unit generates a document including a draft of an invoice amount for the transaction based on the data.
Citation Information
Patent Citations
Support method of procurement of building material and equipment
JP2003132251A
Support system for specific inspection, supporting method for specific inspection, and program
JP2019060741A
Credit decision data providing system for construction industry
JP2020129168A