Information processing method, program, and information processing device

Abstract

To provide site managers and other relevant parties with information processing methods, etc., that provide information regarding the progress of construction work. [Solution] The information processing method displays multiple construction identification information for the construction project to be managed in a first direction, and multiple monitoring items, including milestones indicating priority management items, equipment delivery, and equipment ordering, in a second direction. When the monitoring items of the construction identification information satisfy predetermined warning conditions, the computer performs a process to display warning information at the corresponding position within the grid-like frame formed by the first and second directions.

Description

Technical Field

[0001] The present invention relates to an information processing method, a program, and an information processing apparatus.

Background Art

[0002] There has been proposed a process management apparatus that supports the independent judgment of each worker by displaying the progress status of construction work on a portable device possessed by a user such as a worker (Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] According to the process management method of Patent Document 1, the stress of the worker can be reduced by the worker himself / herself grasping the overall situation and independently judging the order of starting work and the like.

[0005] However, the process management apparatus of Patent Document 1 cannot handle matters that cannot be adjusted only by the ingenuity of individual workers. For such matters, judgment and support by related persons such as on-site agents in charge of individual construction sites, the supervisors of on-site agents, and the persons in charge of support departments are required.

[0006] In one aspect, it is an object to provide an information processing method and the like that provide information regarding the progress status of construction work to on-site agents and related persons.

Means for Solving the Problems

[0007] <00000�6>The information processing method involves displaying multiple construction identification information for the construction project to be managed in a first direction, and displaying multiple monitoring items, including milestones indicating key management items, equipment delivery, and equipment ordering, in a second direction. When the monitoring items of the construction identification information meet predetermined warning conditions, the computer performs a process to display warning information at the corresponding position within the grid-like frame formed by the first and second directions. [Effects of the Invention]

[0008] In one respect, it can provide information processing methods, etc., to site managers and related parties regarding the progress of construction work. [Brief explanation of the drawing]

[0009] [Figure 1] This is an explanatory diagram illustrating the overview of the construction support system. [Figure 2] This is an explanatory diagram illustrating the configuration of the construction support system. [Figure 3] This is an explanatory diagram illustrating the record layout of the milestone database. [Figure 4] This is an explanatory diagram illustrating the record layout of the equipment list database. [Figure 5] This is an explanatory diagram illustrating the record layout of the log database. [Figure 6] This is an explanatory diagram illustrating the record layout of the implementation plan database. [Figure 7] This is an explanatory diagram illustrating the record layout of various government databases. [Figure 8] This is an explanatory diagram illustrating the record layout of the judgment result database. [Figure 9] This is an example of a project list screen. [Figure 10] Figure 9 is an enlarged view of section X. [Figure 11] This is an example of a milestone alert screen. [Figure 12] This is an enlarged view of section XII in Figure 11. [Figure 13]It is an enlarged view of part XIII in FIG. 11. [Figure 14] It is an example of the alert screen for the delivery date of material A. [Figure 15] It is an enlarged view of part XV in FIG. 14. [Figure 16] It is an enlarged view of part XVI in FIG. 14. [Figure 17] It is an example of the alert screen for the order date of material A. [Figure 18] It is an enlarged view of part XVIII in FIG. 17. [Figure 19] It is an enlarged view of part XIX in FIG. 17. [Figure 20] It is an example of the alert screen for the submission status of the safety log. [Figure 21] It is an example of the alert screen for the creation status of the implementation plan. [Figure 22] It is an example of the alert screen for the submission status to various government agencies. [Figure 23] It is an example of the construction home screen. [Figure 24] It is an enlarged view of part XXIV in FIG. 23. [Figure 25] It is an enlarged view of part XXV in FIG. 23. [Figure 26] It is an enlarged view of part XXVI in FIG. 23. [Figure 27] It is an enlarged view of part XXVII in FIG. 23. [Figure 28] It is an enlarged view of part XXVIII in FIG. 23. [Figure 29] It is an example of the approaching deadline screen. [Figure 30] It is an enlarged view of part XXX in FIG. 29. [Figure 31] It is an enlarged view of part XXXI in FIG. 29. [Figure 32] It is an enlarged view of part XXXII in FIG. 29. [Figure 33] It is a flowchart explaining the processing flow of the program during data input. [Figure 34] [[ID=]It is a flowchart explaining the processing flow of the program during data viewing. [Figure 35] This is a flowchart illustrating the processing flow of a program that creates a judgment result database. [Figure 36] This is a flowchart illustrating the processing flow of a program that creates a judgment result database. [Figure 37] This is a flowchart illustrating the processing flow of a program that creates a judgment result database. [Figure 38] This is a flowchart illustrating the processing flow of a program that creates a judgment result database. [Figure 39] This is a flowchart illustrating the processing flow of a program that creates a judgment result database. [Figure 40] This is a flowchart illustrating the processing flow of a program that creates a judgment result database. [Figure 41] This is a flowchart illustrating the processing flow of a program that creates a judgment result database. [Figure 42] This is a flowchart illustrating the processing flow of a program that creates a judgment result database. [Figure 43] This is an explanatory diagram illustrating the configuration of the construction support system in Embodiment 2. [Modes for carrying out the invention]

[0010] [Embodiment 1] In construction projects, a site representative is appointed who has the authority to act on behalf of the general contractor in legal matters. The site representative has the same authority as the general contractor's representative director at the construction site they are responsible for.

[0011] The site manager is usually an employee of the general contractor and is responsible for overseeing all aspects of the construction work, including schedule management and safety management. The content of each construction project differs, and no two construction projects are exactly alike. The site manager is required to make appropriate judgments on a daily basis, depending on the situation.

[0012] Construction progress can be affected by weather conditions and other factors. For example, if progress is delayed due to bad weather, it is the responsibility of the site manager to readjust the deployment of site workers and the schedule of construction machinery.

[0013] The site manager's job also includes managing the delivery dates of various equipment to be installed at the construction site, as well as submitting various notifications and permits to government agencies at the appropriate time. As you can see, the site manager's duties are diverse and demanding.

[0014] On the other hand, site managers are sometimes selected from among the general contractor's younger to mid-career employees. Even those who have received sufficient training and practical experience beforehand may feel pressured to make decisions and manage a construction site as the person in charge, given the ever-changing circumstances.

[0015] Furthermore, with the enforcement of the Work Style Reform Act, restrictions on overtime hours for site managers have become stricter. Therefore, it is necessary for site managers' superiors and staff in the back-office departments, as well as other stakeholders, to understand the site managers' work situation and provide appropriate support. The information processing method of this embodiment can support site managers by providing information on the progress of construction work to their superiors and other stakeholders, thereby ensuring that appropriate support is provided to them.

[0016] If a site manager is overworked due to insufficient support, they may be unable to continue working due to mental health issues or other problems. In other words, the information processing methods of this embodiment contribute to protecting everyone's right to work, promoting a safe and secure work environment, increasing meaningful and humane work, and creating and implementing a global strategy for young people's employment.

[0017] Furthermore, if site managers do not receive sufficient support and make mistakes in the planning process, it may become impossible to proceed with construction work as planned. The information processing methods and other aspects of this embodiment contribute to increasing economic productivity through diversification, technological advancement, and innovation by providing appropriate support to site managers.

[0018] Construction work creates infrastructure, housing, and public facilities. The information processing method of this embodiment contributes to creating high-quality, reliable, sustainable, and disaster-resistant infrastructure; ensuring that everyone can live in adequate and safe housing at an affordable price and have access to basic services; and ensuring that everyone can use safe and accessible green spaces and public areas.

[0019] Figure 1 is an explanatory diagram illustrating the overview of the construction support system 10. The site manager uses an information processing device 20, such as a personal computer, smartphone, or tablet, to create various documents such as construction plans and progress reports. The created documents are sent to the server 30 as they are created. Note that document creation may be handled not only by the site manager themselves, but also by an assistant engineer or other person.

[0020] When milestones outlined in the plan are approaching, for example, a notification is sent from the server 30 to the site representative's information processing device 20. By checking the notification, the site representative can prevent important deadlines from being missed.

[0021] The site manager's supervisor will review documents prepared by their subordinates and approve them if necessary. The supervisor will communicate with their subordinates by any means possible, such as telephone, email, or in person, to provide advice, information, and other support. Back-office staff and other site support personnel will also review documents related to their assigned sites and provide support to the site manager as needed.

[0022] For example, if a site manager is overwhelmed with work, they may not be able to make specific requests for support to their supervisor and support staff. Even in such cases, supervisors and support staff can proactively provide support based on progress reports submitted routinely, such as daily, weekly, or monthly reports. In the following explanation, progress reports such as daily, weekly, and monthly reports may be collectively referred to as "logs."

[0023] If even the regular submission of daily logs is delayed, supervisors and support staff can infer that the site representative is in need of assistance based on the fact that the required documents have not been submitted at the prescribed time.

[0024] In the following explanation, we will use the example of a site manager as the user of the construction support system 10 at the construction site. In addition to the site manager, the site manager's assistant or the team leaders of each department may also be users of the construction support system 10.

[0025] Each user can learn how experienced senior colleagues work by viewing documents created by them, for example, and improve their own skills. As a result, by utilizing the construction support system 10, each user, including site managers, can improve their work skills and increase work efficiency.

[0026] Figure 2 is an explanatory diagram illustrating the configuration of the construction support system 10. As mentioned above, the construction support system 10 includes a server 30 and multiple information processing devices 20 that can communicate with each other via a network.

[0027] The information processing device 20 comprises a control unit 21, a main memory 22, an auxiliary memory 23, a communication unit 24, a display unit 25, an input unit 26, and a bus. The control unit 21 is an arithmetic control device that executes the program of this embodiment. One or more CPUs (Central Processing Units), GPUs (Graphics Processing Units), or multi-core CPUs are used in the control unit 21. The control unit 21 is connected to each hardware component of the information processing device 20 via the bus.

[0028] The main memory 22 is a storage device such as SRAM (Static Random Access Memory), DRAM (Dynamic Random Access Memory), or flash memory. The main memory 22 temporarily stores information necessary during processing performed by the control unit 21 and the program currently being executed by the control unit 21.

[0029] The auxiliary storage device 23 is a storage device such as SRAM, flash memory, hard disk, or magnetic tape. The auxiliary storage device 23 stores the milestone DB (Database) 41, the device list DB 42, the program to be executed by the control unit 21, and various data necessary for the execution of the program.

[0030] The communication unit 24 is an interface that facilitates communication between the information processing device 20 and a network or other devices. As mentioned above, the information processing device 20 is a general-purpose information device used by individual users, such as a personal computer, smartphone, or tablet. The information processing device 20 may also be dedicated hardware manufactured specifically for the construction support system 10 of this embodiment.

[0031] The display unit 25 is, for example, a liquid crystal display device or an organic EL (Electro-Luminescence) display device. The input unit 26 is, for example, an input device such as a keyboard, mouse, trackball, or microphone. The display unit 25 and the input unit 26 may be stacked together to form a touch panel.

[0032] The server 30 comprises a control unit 31, a main memory 32, an auxiliary memory 33, a communication unit 34, and a bus. The control unit 31 is an arithmetic control device that executes the program of this embodiment. One or more CPUs, GPUs, or multi-core CPUs are used in the control unit 31. The control unit 31 is connected to each hardware component of the server 30 via the bus.

[0033] The main memory 32 is a storage device such as SRAM, DRAM, or flash memory. The main memory 32 temporarily stores information necessary during processing performed by the control unit 31 and the program currently being executed by the control unit 31.

[0034] The auxiliary storage device 33 is a storage device such as SRAM, flash memory, hard disk, or magnetic tape. The auxiliary storage device 33 stores the milestone DB 41, equipment list DB 42, log DB 43, implementation plan DB 44, government agency DB 45, judgment result DB 46, programs to be executed by the control unit 31, and various data necessary for program execution. The milestone DB 41, equipment list DB 42, log DB 43, implementation plan DB 44, government agency DB 45, and judgment result DB 46 may be stored in an external mass storage device connected to the server 30.

[0035] The communication unit 34 is an interface that facilitates communication between the server 30 and the network or other devices.

[0036] Server 30 is a mainframe computer, a virtual machine running on a mainframe computer, multiple personal computers performing distributed processing, or a cloud computing system. Server 30 may also be a general-purpose personal computer or information device such as a tablet.

[0037] Figure 3 is an explanatory diagram illustrating the record layout of the Milestone DB41. The Milestone DB41 is a database that records milestones at each site and their status in relation to each milestone. In the following explanation, unless otherwise specified, the "current" date will be June 19, 2024 as an example.

[0038] Milestone DB41 has the following fields: Site Name, Expired Count, Nearing Expired Count, Milestone, Importance, Status, Scheduled Date, Scheduled Date Type, Actual Date, Actual Date Type, Person in Charge, Submission Destination, Type, Expired, Nearing Expired, and Follow-up. The Milestone field has a Major Item field, a Minor Item field, and a Milestone Name field.

[0039] The Site Name field records a name that identifies the construction site. Alternatively, a Site ID (Identifier) ​​uniquely assigned to each site may be used instead of the Site Name. The Expired Count field records the number of records for which the Expired Count field (described later) has an "ON" flag. The Nearing Expiration Count field records the number of records for which the Nearing Expiration Count field (described later) has an "ON" flag. The control unit 31 automatically updates the Expired Count field and the Nearing Expiration Count field when a record is updated.

[0040] The major category field, minor category field, and milestone name field record the major category, minor category, and name of the milestone, respectively. The milestone field may also have subcategory fields, for example. The importance field records the importance of the milestone. The status field records the progress of the milestone.

[0041] The "Scheduled Date" field records the scheduled date. The "Scheduled Date Type" field records the type of scheduled date. The "Scheduled Date Type" is not limited to "Scheduled Creation Date" as exemplified in Figure 3. For example, "Scheduled Approval Date," "Scheduled Submission Date," etc., may be recorded in the "Scheduled Date Type" field.

[0042] The Actual Date field records the actual date on which the milestone was executed. The Actual Date Type field records the type of the actual date. In Figure 3, since each milestone has not yet been executed, the Actual Date field is blank. It is desirable that the Actual Date Type field records the type corresponding to the Scheduled Date Type field.

[0043] The "Assigned Person" field records the name of the person in charge of each milestone. The "Submission Destination" field records the destination for documents related to the milestone. For milestones where no documents need to be submitted, the "Submission Destination" field is left blank. The "Type" field records the type of milestone. Milestone types include, for example, planning, listing, intermediate inspection, and final inspection.

[0044] The expired field records a flag indicating whether or not the milestone's execution deadline has passed. The default value for the expired field is the "OFF" flag. The control unit 31 records the "ON" flag in the expired field if the scheduled date has passed but the actual date has not been recorded.

[0045] The "Approaching Deadline" field records a flag indicating whether the deadline for the milestone is approaching. The default value for the "Expired" field is the "OFF" flag. The control unit 31 records the "ON" flag in the "Approaching Deadline" field if the number of days until the scheduled date is below the threshold but no actual date has been recorded. Note that the threshold used for determination may differ for each site or milestone item.

[0046] The Follow field records a flag indicating whether or not a supervisor or other supervisor communicated with the site representative to follow up on the progress. The default value for the Follow field is the "OFF" flag. When the control unit 31 receives input indicating that follow-up has been performed, it records the "ON" flag in the Follow field. The control unit 31 may update the record in the Follow field based on a log created by the supervisor or site representative, or a communication record between the supervisor and the site representative. The Milestone DB 41 has one record for each milestone.

[0047] The site manager fills in data in the milestone field, importance field, scheduled date field, and scheduled date type field when formulating the construction plan. Specifically, the site manager edits the milestone DB 41 via the information processing device 20 and the network.

[0048] For example, a site manager sends a plan created in a known format such as a PERT (Program Evaluation and Review Technique) diagram or a Gantt chart to the server 30. The control unit 31 automatically records data in the milestone field and importance field based on the received plan.

[0049] The site manager updates the data in the status field, actual date field, and actual date type field whenever there is a change in the situation. The control unit 31 may automatically update the status field, actual date field, and actual date type field based on log data or other data.

[0050] In addition to the fields shown in Figure 3, the milestone DB41 may also have fields such as a comment field for recording comments from stakeholders regarding each milestone.

[0051] Figure 4 is an explanatory diagram illustrating the record layout of the equipment list DB42. The equipment list DB42 is a database that records the status of various types of equipment, referred to as "Type A" equipment. Type A equipment includes lighting fixtures, air conditioning equipment, distribution boards, switchboards, fire alarms, etc.

[0052] The equipment list DB42 has fields for site name, planning stage, ordering stage, and delivery stage. The planning stage field includes fields for equipment name, manufacturer, distributor, scheduled delivery start date, scheduled delivery end date, and acceptance date. The ordering stage field includes fields for production period, order confirmation date, actual order date, and order delay. The delivery stage field includes fields for actual delivery date, pre-confirmation days, pre-confirmation date, delay confirmation days, delay confirmation date, and delivery delay. The equipment list DB42 has one record for each piece of equipment.

[0053] The Site Name field records the name that identifies the construction site. The Equipment Name field records the general name of the equipment to be installed. The Manufacturer Field records the name of the company that manufactures the equipment. The Distributor Field records the name of the distributor that delivers the equipment.

[0054] In the manufacturer field, "Unregistered Manufacturer" indicates that the manufacturer is not registered in the so-called master database. In the agent field, "Not Subject to Ordering" indicates that the site representative does not need to place an order, for example, because the client provides the materials in kind.

[0055] The scheduled start and end dates for delivery of the equipment are recorded in the "Scheduled Delivery Start Date" and "Scheduled Delivery End Date" fields. The "Acceptance Date" field records the date on which the customer, such as the contractor, approved the equipment to be used. The "Planning Stage" field may also include fields for recording the equipment model number and the quantity of equipment, etc.

[0056] The Production Period field records the production period required from the time the equipment is ordered until it is delivered. The Order Confirmation Date field records the final date on which the order should be placed, calculated from the scheduled delivery start date and the production period. The Actual Order Date records the date on which the order was actually placed. The Order Delay field records a flag indicating whether the order is delayed or not. The default value for the Order Delay field is the "OFF" flag. If the Order Confirmation Date has passed but the Actual Order Date has not been recorded, the control unit 31 records the "ON" flag in the Order Delay field.

[0057] The "Delivery Date" field records the date on which the delivery of the equipment actually began. The "Pre-Confirmation Days" field records the number of days before the scheduled delivery start date that the delivery date should be confirmed with the distributor or other relevant party. In Figure 4, the pre-confirmation days and the production period are the same, but they may be different.

[0058] The "Pre-Confirmation Date" field records the date on which the delivery date was confirmed with the agent, etc. The "Delay Confirmation Days" field records the number of days on which a delay in the delivery date has been confirmed. The "Delay Confirmation Date" field records the date on which the delay in the delivery date was confirmed. The "Delivery Delay" field records a flag indicating whether or not the delivery is delayed. The default value for the "Delivery Delay" field is the "OFF" flag. The control unit 31 records the "ON" flag in the "Delivery Delay" field if there are no recorded actual delivery dates that have passed the scheduled delivery start date.

[0059] The site manager fills in data in the site name field, equipment name field, manufacturer field, distributor field, scheduled delivery start date field, and scheduled delivery end date field when formulating the construction plan. The control unit 31 may also automatically record data in these fields based on the plan.

[0060] The site representative enters data in the Acceptance Date field, Production Period field, Order Confirmation Date field, Order Actual Date field, Delivery Actual Date field, Pre-Confirmation Days field, Delay Confirmation Days field, and Delay Confirmation Date field based on the progress of negotiations with the agent, etc. The control unit 31 may automatically record data in these fields based on, for example, a log, emails sent and received by the site representative, or data from an order management system (not shown in the diagram).

[0061] Figure 5 is an explanatory diagram illustrating the record layout of the log DB43. The log DB is a database that records logs submitted by the site manager. In the following explanation, a construction site where logs are submitted monthly will be used as an example. The log DB43 has a project name field, a project number field, a year and month field, and a file field.

[0062] The Project Name field records the project name. The Project Name field may also record the site name or a site ID unique to each site. The Project Number field records the project number assigned to each project. The Year and Month field records the year and month in which the log should be submitted. The File field records the submitted log, or the file name of the submitted log. A "-" in the File field indicates that the log has not been submitted despite the submission deadline having passed. Log DB43 has one record for each submission deadline.

[0063] Figure 6 is an explanatory diagram illustrating the record layout of the Implementation Plan DB44. The Implementation Plan DB44 is a database that records the status of the construction implementation plan. The construction implementation plan refers to a plan that outlines the amount and timing of the budget required for carrying out the construction work.

[0064] The implementation plan DB44 has fields for project number, project name, start date, budget creation status, approval date, and implementation. The project number field records the project number assigned to each project. The project name field records the project name. The project name is associated with the site name recorded in the milestone DB41 and equipment list DB42 (databases not shown in the diagram), and once the site name is determined, the project name and project number are also uniquely determined.

[0065] The "Start Date" field records the start date of the construction work. The "Budget Creation Status" field records the status of the budget creation, i.e., the creation of the implementation plan. "Approved" indicates that the created budget has been approved. "Not Created" indicates that the budget has not yet been created. The "Approval Date" field records the approval date. If the budget is not approved, the "Approval Date" field is blank.

[0066] The Implementation field records flags related to the implementation plan. The default value for the Implementation field is the "OFF" flag. The control unit 31 records the "ON" flag in the Implementation field if one month has passed since the start date and the approval date has not been recorded.

[0067] Figure 7 is an explanatory diagram illustrating the record layout of the Government Offices DB45. The Government Offices DB45 is a database that records the status of documents submitted to government offices and other public institutions. In the following explanation, documents submitted to government offices may be referred to as government notification forms. The Government Offices DB45 has the following fields: Site Name, Submitted Document, Scheduled Submission Date, Permit Acceptance Date, Initial Delay Confirmation Date, and Document. The Government Offices DB45 has one record for each document.

[0068] The Site Name field records a name that identifies the construction site. The Documents to be Submitted field records the names of the documents to be submitted to government agencies. The Scheduled Submission Date field records the scheduled date for submitting the documents to government agencies. If no scheduled submission date is set, the Scheduled Submission Date field is left blank.

[0069] The "Permission Acceptance Date" field records the date the permission was received from the government agency. If permission has not been received, the "Permission Acceptance Date" field will be blank. The "Initial Delay Confirmation Date" field records the date the delay in document submission was confirmed. If no submission delay was confirmed, the "Initial Delay Confirmation Date" field will be blank.

[0070] The document field records a flag indicating the delay in submitting documents. The default value for the document field is the "OFF" flag. The control unit 31 records the "ON" flag in the document field if the scheduled submission date field is blank or if the date recorded in the scheduled submission date field has passed.

[0071] Figure 8 is an explanatory diagram illustrating the record layout of the Judgment Result DB46. The Judgment Result DB46 is a database that records information regarding the necessity of warning information, determined based on flags recorded in the Milestone DB41, Equipment List DB42, Logbook DB43, Implementation Plan DB44, and Government Agency DB45.

[0072] The Judgment Result DB46 contains the following fields: Site Name, Milestone, A Delivery, A Order, Log, Implementation, and Government. The Milestone field includes an Expired and Nearing Expiration fields. The Judgment Result DB46 contains one record for each site name.

[0073] The Site Name field records a name that can identify the construction site. The Expired Field records a flag indicating whether or not warning information regarding the expiration of the milestone is required. In the milestone DB41 described using Figure 3, the control unit 31 records "ON" in the Expired Count field if a value other than "0" is recorded in the Expired Count field, and records "OFF" in the Expired Count field if "0" is recorded in the Expired Count field.

[0074] The "Approaching Deadline" field records a flag indicating whether or not warning information is needed regarding the existence of milestones that are approaching their deadline. In the milestone DB41 described using Figure 3, the control unit 31 records "ON" in the "Approaching Deadline" field if a value other than "0" is recorded in the "Approaching Deadline Count" field, and records "OFF" in the "Approaching Deadline" field if "0" is recorded in the "Approaching Deadline Count" field.

[0075] The A Delivery field records a flag indicating whether or not warning information regarding the delivery status of material A, as explained using Figure 4, is necessary. The control unit 31 records "ON" in the A Delivery field if there is a record in the equipment list DB 42, as explained using Figure 4, where the "ON" flag is recorded in the Delivery Delay field, and records "OFF" in the A Delivery field otherwise.

[0076] The A Order field records a flag indicating whether or not warning information regarding the ordering status of material A, as explained using Figure 4. The control unit 31 records "ON" in the A Order field if there is a record in the equipment list DB 42, as explained using Figure 4, where the "ON" flag is recorded in the Order Delay field, and records "OFF" in the A Delivery field otherwise.

[0077] The log field contains a flag indicating whether or not warning information regarding the log submission status is required, as explained using Figure 5. The control unit 31 records "ON" in the log field if there is a record in the log DB 43, as explained using Figure 5, where "-" is recorded in the file field, and records "OFF" in all other cases.

[0078] The implementation field contains a flag indicating whether or not warning information regarding the implementation plan, as explained using Figure 6, is necessary. The control unit 31 records an "ON" flag in the implementation field of the judgment result DB46 if there is a record in the implementation field of the implementation plan DB44, as explained using Figure 6, that has an "ON" flag recorded in it. Otherwise, it records an "OFF" flag in the implementation field of the judgment result DB46.

[0079] The government office field contains a flag indicating whether or not warning information regarding the status of documents submitted to government offices, as explained using Figure 7, is necessary. The control unit 31 records an "ON" flag in the government office field of the determination result DB 46 if there is a record in the document field of the government office DB 45, as explained using Figure 7, where the "ON" flag is recorded. Otherwise, it records an "OFF" flag in the government office field of the determination result DB 46.

[0080] The Expired Field, Nearing Expiry Field, A Delivery Field, A Order Field, Log Field, Execution Field, and Government Field are all fields related to monitoring items. The conditions for recording the "ON" flag in each of the monitoring item fields described above are the conditions that satisfy the warning conditions for each project identification information.

[0081] Furthermore, the monitoring items used when monitoring the progress of construction are not limited to the seven items recorded in the seven fields mentioned above. The seven items mentioned above are examples of high-priority, key monitoring items. The key monitoring items may be only a part of the seven items mentioned above.

[0082] The control unit 31 automatically updates the relevant records in the judgment result DB 46 when the milestone DB 41, equipment list DB 42, logbook DB 43, implementation plan DB 44, or government agency DB 45 are updated.

[0083] Figure 9 shows an example of the project list screen. The project list screen displays a list of the status of projects under management. At the top of the project list screen is a search criteria field 66 where the user can enter search criteria. The user can specify various search criteria, such as site name, project number, and site manager name. Default search criteria may be set for each user using the project support system 10.

[0084] The control unit 21 acquires data from the server 30, etc., via the network and displays the following screens on the display unit 25. In the following description, the process by which the control unit 21 acquires various data may be omitted.

[0085] A search button and a clear button are located in the lower right corner of the search criteria field. When the user selects the search button, the control unit 21 retrieves data from a business management system (not shown in the diagram) based on the conditions set in the search criteria field.

[0086] Below the search criteria field, there is a project list field 61. In the project list field 61, various information such as the representative project number, site name, and site manager name for multiple projects is displayed in a table format. The control unit 21 formats the data acquired from the business management system into a table format and displays it in the project list field 61.

[0087] In other words, in the vertical direction of the construction list column 61, construction identification information such as the representative construction number and site name is arranged side by side. Note that the construction identification information may be either the representative construction number or the site name. In the horizontal direction of the construction list column 61, items related to each construction are arranged.

[0088] In the following explanation, the direction in which the construction identification information is arranged may be referred to as the first direction, and the direction in which the items related to each construction are arranged may be referred to as the second direction. Figure 9 is a table having a grid-like frame formed by the first direction and the second direction. In Figure 9, the first direction is the vertical direction, and the second direction is the horizontal direction. Multiple construction identification information for the constructions to be managed are displayed in the first direction. The control unit 21 may be arranged with the first direction in the horizontal direction and the second direction in the vertical direction.

[0089] Figure 10 is an enlarged view of section X in Figure 9. The top row, which shows the items in the second direction, displays the headings "My...", "A Delivery", "A Order", "Log", "Implementation", and "Government Office". These headings each indicate key management items related to the progress of the construction work. In other words, the second direction displays multiple monitoring items, including milestones indicating key management items, equipment delivery, and equipment ordering.

[0090] "My..." is an abbreviation for "Milestone". "A Delivery" is an abbreviation for "Delivery of Equipment". "A Order" is an abbreviation for "Order for Equipment". "Implementation" is an abbreviation for "Implementation Plan". "Government" is an abbreviation for "Government Notification". If there is sufficient space in the display area of ​​display unit 25, it may also be displayed as "Milestone" and "Delivery of Equipment".

[0091] A first mark 511 or a second mark 512 is displayed at a position corresponding to each item within a grid-like frame formed by a first direction and a second direction. The first mark 511 is an example of warning information indicating that a priority monitoring item is in a warning state. The second mark 512 is an example of non-warning information indicating that a priority monitoring item is in a non-warning state. The shape and color of the first mark 511 and the second mark 512 are arbitrary. It is desirable that the first mark 511 be in a form that is easily intuitively recognizable as warning information, for example, by being red. The control unit 21 may leave the grid-like frame blank instead of displaying the second mark 512.

[0092] Figure 11 shows an example of the milestone alert screen. When the first mark 511 displayed in the "My..." column is selected in the screen described using Figure 10, the control unit 21 displays the milestone alert screen shown in Figure 11. The milestone alert screen displays a list of data related to the record in the milestone DB 41 where the expired field is in the "ON" state, which is the reason why the first mark 511 is displayed in the "My..." column.

[0093] At the top of the milestone alert screen is the project name field 71. The project name field 71 displays the project name corresponding to the first mark 511 selected by the user.

[0094] Below the project name field 71, there is a search criteria field 66. Users can specify various search criteria, such as milestone name, importance, scheduled date, and actual date. Below the search criteria field 66, the milestone field 62 and the schedule field 63 are located side by side.

[0095] Figure 12 is an enlarged view of section XII in Figure 11. Figure 12 is an enlarged view of the upper left of the milestone column 62. The milestone column 62 displays the status of each milestone related to the construction project shown in the project name column 71. Specifically, the milestone column 62 displays in tabular format the data recorded in the actual date type field from the milestone field of the milestone DB 41, as explained using Figure 3.

[0096] The rectangle on the far left of the Milestone column 62 is a checkbox that accepts user selections. The operation column to its right contains buttons that allow users to request the display of operation menus related to each milestone item. The due date column to the right of that displays the data recorded in the expired field of Milestone DB 41 as "×" if it is "ON" and blank if it is "OFF".

[0097] In the Follow column to the right, the data recorded in the Follow field of Milestone DB41 is displayed as a check mark if it is "ON" and as a blank space if it is "OFF".

[0098] Figure 13 is an enlarged view of section XIII in Figure 11. Figure 13 is an enlarged view of the upper part of the schedule column 63. A scale indicating the year and month is located at the top of the schedule column 63. Figure 13 shows an example of the screen displayed in June 2024. The scale indicating June 2024 is displayed prominently with a thick border. In the schedule column 63, the date recorded in the scheduled date field of the milestone DB 41 is displayed as a black inverted triangle.

[0099] The milestone alert screen, as explained using Figures 11 to 13, allows users to easily understand the status of milestones. Site managers can understand the progress of their assigned milestones and take necessary actions. Site managers and other supervisors can understand the progress of their subordinates' milestones and determine whether follow-up is necessary.

[0100] Figure 14 shows an example of the A material delivery date alert screen. When the first mark 511 displayed in the "A delivery" column in the screen described using Figure 10 is selected, the control unit 21 displays the A material delivery date alert screen shown in Figure 14. In Figure 14, the A material delivery date alert screen is superimposed on the center of the previously displayed screen. The previously displayed screen is dimmed.

[0101] The delivery alert screen displays a list of data related to the records in the equipment list DB42 where the delivery delay flag is "ON," which is the reason why the first mark 511 is displayed in the "A Delivery" column.

[0102] At the top of the A material delivery date alert screen, there is a project name field 71. The project name field 71 displays the project name corresponding to the first mark 511 that was selected by the user.

[0103] Figure 15 is an enlarged view of section XV in Figure 14. Figure 16 is an enlarged view of section XVI in Figure 14. Figure 16 is displayed immediately to the right of Figure 15. Figures 15 and 16 will be used to explain the A material delivery date alert screen.

[0104] At the top of Figure 15, a major heading titled "List of Specifications for Delivery of Major Equipment" is displayed. Below this major heading, subheadings for "Equipment Name," "Manufacturer," "Distributor," "Scheduled Delivery Start Date," and "Acceptance Date" are displayed.

[0105] The columns "Equipment Name," "Manufacturer," "Distributor," "Scheduled Delivery Start Date," and "Acceptance Date" display the data recorded in the Equipment Name field, Manufacturer field, Distributor field, Scheduled Delivery Start Date field, and Acceptance Date field of the equipment list DB42, as explained using Figure 4.

[0106] At the top of Figure 16, a major category titled "Delivery Start Date" is displayed. Below this major category, subcategories are displayed: "Actual Date," "Days for Pre-Confirmation," "Date for Pre-Confirmation," "Days for Delay Confirmation," and "Date for Delay Confirmation." In Figure 16, "Actual Date" refers to the "Actual Delivery Start Date."

[0107] The columns "Actual Delivery Date," "Pre-Confirmation Days," "Pre-Confirmation Date," "Delay Confirmation Days," and "Delay Confirmation Date" display the data recorded in the Delivery Actual Delivery Date field, Pre-Confirmation Days field, Pre-Confirmation Date field, Delay Confirmation Days field, and Delay Confirmation Date field of the equipment list DB42, as explained using Figure 4.

[0108] As explained using Figures 14 to 16, the A material delivery date alert screen allows users to easily understand the delivery status of equipment. Site managers can understand the delivery status of equipment and take necessary actions. Supervisors of site managers can understand the delivery status of equipment related to the sites they are in charge of and determine whether follow-up is necessary.

[0109] Figure 17 shows an example of the A material order date alert screen. When the first mark 511 displayed in the "A Order" column in the screen described using Figure 10 is selected, the control unit 21 displays the A material order date alert screen shown in Figure 17. In Figure 17, the A material order date alert screen is superimposed on the center of the previously displayed screen. The previously displayed screen is dimmed.

[0110] The A material order date alert screen displays a list of data related to the records in the equipment list DB42 where the order delay flag is "ON," which is the reason why the first mark 511 is displayed in the "A Order" column.

[0111] At the top of the A material order date alert screen, there is a project name field 71. The project name field 71 displays the project name corresponding to the first mark 511 that was selected by the user.

[0112] Figure 18 is an enlarged view of section XVIII in Figure 17. Figure 19 is an enlarged view of section XIX in Figure 17. Figure 19 is displayed immediately to the right of Figure 18. Figures 18 and 19 will be used to explain the A material order alert screen.

[0113] At the top of Figure 18, the main heading "List of Specifications for Delivery of Major Equipment" is displayed. This main heading extends from Figure 18 to the left half of Figure 19. Below the main heading "List of Specifications for Delivery of Major Equipment," Figure 18 displays the subheadings "Equipment Name," "Manufacturer," and "Distributor," while Figure 19 displays the subheadings "Scheduled Delivery Start Date" and "Scheduled Delivery End Date." Figure 19 also displays the items "Manufacturing Period," "Order Confirmation Date," and "Actual Order Date."

[0114] The columns "Equipment Name," "Manufacturer," "Distributor," "Scheduled Delivery Start Date," "Scheduled Delivery End Date," "Manufacturing Period," "Order Confirmation Date," and "Actual Order Date" display the data recorded in the Equipment Name field, Manufacturer field, Distributor field, Scheduled Delivery Start Date field, Scheduled Delivery End Date field, Manufacturing Period field, Order Confirmation Date field, and Actual Order Date field of the equipment list DB42, as explained using Figure 4.

[0115] The A-material order date alert screen, as explained using Figures 17 to 19, allows users to easily understand the order and delivery status of equipment. Site managers can understand the equipment order status and take necessary actions. Supervisors of site managers can understand the equipment order status for the sites they are in charge of and determine whether follow-up is necessary.

[0116] Figure 20 shows an example of the safety log submission status alert screen. In the screen described using Figure 10, if the first mark 511 or the second mark 512 displayed in the "Log" column is selected, the control unit 21 displays the safety log submission status alert screen shown in Figure 20. As with Figures 14 and 17, the safety log submission status alert screen is superimposed on the center of the previously displayed screen.

[0117] At the top of the safety log submission status alert screen, there is a project name field 71. The project name field 71 displays the project name corresponding to the first mark 511 or second mark 512 selected by the user.

[0118] Below the project name column 71, a list is displayed showing the submission status of the logbooks for the construction site corresponding to the project name column 71. The control unit 21 displays the list shown in Figure 20 based on the logbook DB 43. A "〇" in the "Submission Status" column indicates that the logbook has been submitted, while "Not Submitted" indicates that the logbook has not been submitted.

[0119] The safety log submission status alert screen, as explained using Figure 20, allows users to easily understand the status of log submissions. Supervisors of site managers can understand the log submission status of their subordinates and decide whether follow-up is necessary. The control unit 21 may also display the corresponding log on the display unit 25 based on click operations or other actions received on the safety log submission status alert screen.

[0120] Figure 21 shows an example of the implementation plan creation status alert screen. In the screen described using Figure 10, if the first mark 511 or the second mark 512 displayed in the "Implementation" column is selected, the control unit 21 displays the implementation plan creation status alert screen shown in Figure 21. As with Figures 14 and 17, the implementation plan creation status alert screen is superimposed on the center of the previously displayed screen.

[0121] At the top of the implementation plan creation status alert screen, there is a project name field 71. The project name field 71 displays the project name corresponding to the first mark 511 or second mark 512 selected by the user.

[0122] Below the project name column 71, a list is displayed showing the status of the creation of implementation plans for the construction site corresponding to the project name column 71. The control unit 21 displays the list shown in Figure 21 based on the implementation plan DB 44.

[0123] The implementation plan creation status alert screen, as explained using Figure 21, allows users to easily understand the status of implementation plan creation. Supervisors of site representatives can understand the status of implementation plans created by their subordinates and determine whether follow-up is necessary. The control unit 21 may also display the workflow for approval procedures on the display unit 25 based on click operations, etc., received on the implementation plan creation status alert screen by a person with approval authority. The control unit 21 may also display the corresponding implementation plan on the display unit 25 based on click operations, etc., received on the implementation plan creation status alert screen.

[0124] Figure 22 shows an example of the government submission status alert screen. When the control unit 21 receives a selection of either the first mark 511 or the second mark 512 displayed in the "Government" column in the screen described using Figure 10, it displays the government submission status alert screen shown in Figure 22. As with Figures 14 and 17, the government submission status alert screen is superimposed on the center of the previously displayed screen.

[0125] At the top of the government submission status alert screen, there is a project name field 71. The project name field 71 displays the project name corresponding to the first mark 511 or second mark 512 selected by the user.

[0126] Below the project name column 71, a list is displayed showing the status of documents submitted to various government agencies related to the construction site corresponding to the project name column 71. The control unit 21 displays the list shown in Figure 22 based on the government agency database 45.

[0127] The government submission status alert screen, as explained using Figure 22, allows users to easily understand the status of documents to be submitted to government agencies. Supervisors of on-site representatives can understand the status of documents prepared by their subordinates and determine whether follow-up is necessary. The control unit 21 may also display the corresponding documents on the display unit 25 based on click operations received on the government submission status alert screen. For example, if a government agency inquires about submitted documents, the user can check the documents and respond promptly.

[0128] Figure 23 is an example of the construction home screen. The construction home screen is a screen that aggregates and displays information related to a single construction project. When the control unit 21 receives an operation such as a right-click or double-click on the first mark 511 displayed in the "My..." column, i.e., warning information related to a milestone, in the screen described using Figure 10, the control unit 21 displays the screen of Figure 23 instead of the milestone alert screen described using Figure 11.

[0129] When the selection of the first mark 511 is received, it is desirable that the user can appropriately choose whether to display the screen shown in Figure 11 or the screen shown in Figure 23. For example, when a specific operation such as a right-click is received, the control unit 21 may alternately switch between displaying the screen shown in Figure 11 and the screen shown in Figure 23. In the construction list screen explained using Figure 9, the control unit 21 may display the construction home screen shown in Figure 23 when a construction selection is received.

[0130] At the top of the construction home screen is the project name field 71. The project name field 71 displays the project name corresponding to the first mark 511 selected by the user. Below the project name field 71 are the expired item count field 681 and the nearing item count field 682. The expired item count field 681 and the nearing item count field 682 are examples of displays related to the number of milestones that are subject to warnings.

[0131] Below the Expired Items column 681 and the Nearing Expired Items column 682, the Site Basic Information column 64 is positioned across the full width of the screen. Below the Site Basic Information column 64, the Notices column 67 is positioned on the left and the Site Public Documents column 65 is positioned on the right. The Notices column 67 displays notices for those involved in the construction project shown in the Project Name column 71. At the bottom of the construction home screen, the Milestone column 62 is positioned.

[0132] Figure 24 is an enlarged view of section XXIV in Figure 23. Figure 25 is an enlarged view of section XXV in Figure 23. Figure 24 shows the left portion of the site basic information section 64, and Figure 25 shows the right portion of the site basic information section 64.

[0133] The site basic information section 64 displays basic information about the construction site, such as site ID, site name, construction location, representative construction number, representative project name, construction period, work type classification, property classification, building, contractor, and names of the client and site representative. In large-scale construction projects involving multiple sites, one representative construction number and representative project name will correspond to multiple site IDs and site names.

[0134] Figure 26 is an enlarged view of section XXVI in Figure 23. The section 65 for documents made public to construction personnel, such as parking lot maps and site maps, displays a list including the file name, version number, name of the last updater, and date of the last update.

[0135] For example, site workers use the parking map and site map downloaded from Site Disclosure Documents Section 65 to get to the construction site. Site Disclosure Documents Section 65 may also contain information about any documents to be made public to those involved in the construction, such as the construction schedule, emergency contact information, or important notes.

[0136] Figure 27 is an enlarged view of section XXVII in Figure 23. Figure 28 is an enlarged view of section XXVIII in Figure 23. Figure 27 shows the left portion of the milestone column 62, and Figure 28 shows the right portion of the milestone column 62.

[0137] The milestone column 62 displays information about milestones related to the construction project shown in the project name column 71 that are nearing their deadline. The control unit 21 extracts records from the milestone DB 41, as explained using Figure 3, in which the "Nearly Deadline" field is flagged as "ON". The control unit 21 may also extract records in which the importance field is marked as "High".

[0138] The control unit 21 displays the data recorded in the milestone name field, importance field, responsible person field, submission destination field, scheduled date field, scheduled date type field, and type field of the milestone DB 41, along with the construction number and project name associated with the site name, in a tabular format in the milestone column 62.

[0139] The information displayed in the Importance, Due Date, Due Date Type, and Type columns of the Milestone column 62 is an example of the milestone status. Therefore, the Milestone column 62 displays the name, due date, and status of each milestone.

[0140] Users can easily access information related to the construction project by viewing the project home screen. Therefore, it is desirable for the site manager to inform site workers and engineers from related companies to regularly check the project home screen.

[0141] Figure 29 shows an example of the "Approaching Deadline" screen. When a selection is made in the "Number of Approaching Deadlines" field 682 on the construction home screen, as explained using Figure 23, the control unit 21 displays the "Approaching Deadline" screen shown in Figure 29. The configuration of the "Approaching Deadline" screen is almost identical to that of the milestone alert screen, as explained using Figure 11, and includes the construction project name field 71, the search criteria field 66, the milestone field 62, and the schedule field 63.

[0142] Figure 30 is an enlarged view of section XXX in Figure 29. Figure 31 is an enlarged view of section XXXXI in Figure 29. Figure 32 is an enlarged view of section XXXII in Figure 29. Figure 30 shows the left portion of the milestone column 62, and Figure 31 shows the right portion of the milestone column 62.

[0143] The control unit 21 extracts records in the milestone DB 41, as explained using Figure 3, that have the "ON" flag recorded in the near-deadline field, and displays them in the milestone column 62 of the near-deadline screen. The control unit 21 displays the date recorded in the scheduled date field of the extracted records as a black inverted triangle in the schedule column 63.

[0144] In the construction home screen described using Figure 23, if a selection is made in the expired items column 681, the control unit 21 displays an expired items screen, which is not shown in the diagram. The configuration of the expired items screen is almost identical to that of the milestone alert screen described using Figure 11. The control unit 21 extracts records from the milestone DB 41 described using Figure 3 in which the expired items field has an "ON" flag and displays them in the milestone column 62 of the expired items screen.

[0145] Figure 33 is a flowchart illustrating the processing flow of the program during data entry. The program in Figure 33 is used when a site manager or other personnel operate the information processing device 20 to input or update data into the milestone DB 41, equipment list DB 42, logbook DB 43, implementation plan DB 44, government agency DB 45, and judgment result DB 46, etc.

[0146] The control unit 21 accepts input from the user for items to be entered or updated (step S501). Items include, for example, the site name and information about the database to be entered or updated. The control unit 21 accepts input for data to be entered or updated (step S502). The control unit 21 sends the accepted data to the server 30 (step S503). The control unit 21 terminates processing.

[0147] The control unit 31 receives the data (step S601). The control unit 31 determines the database, record, and field to record the data (step S602). The control unit 31 records the data (step S603).

[0148] A subset of each database recorded in the auxiliary storage device 33 may also be recorded in the auxiliary storage device 23. The control unit 21 may display the data recorded in the auxiliary storage device 23 on the display unit 25 to accept instructions from the user for additional input or updates. The data recorded in the auxiliary storage device 23 is recorded in the auxiliary storage device 33 by a known synchronization process.

[0149] Users may input or update data using natural language. The control unit 21 or control unit 31 can determine the database, records, and fields where the data will be recorded through language analysis.

[0150] Figure 34 is a flowchart illustrating the program's processing flow when viewing data. The program in Figure 34 is used to display the screen described using Figures 9 to 32 on the display unit 25.

[0151] The control unit 21 receives a specification of items to be displayed on the display unit 25 via buttons or the like on the screen (step S511). The items include, for example, the type of screen to display and parameters that specify the data to be displayed. The control unit 21 transmits the received items to the server 30 (step S512).

[0152] The control unit 31 receives the data (step S611). The control unit 31 extracts the data necessary for displaying the received items from each database (step S612). The control unit 31 transmits the extracted data to the information processing device 20 (step S613).

[0153] The control unit 21 receives data (step S513). Based on the received data, the control unit 21 displays the screen described using Figures 9 to 32 on the display unit 25 (step S514). The control unit 21 determines whether or not to terminate the process (step S515). For example, if the user selects the terminate button (not shown), the control unit 21 determines to terminate the process.

[0154] If it is determined that the process should not be terminated (NO in step S515), the control unit 21 returns to step S511. If it is determined that the process should be terminated (YES in step S515), the control unit 21 terminates the process.

[0155] Figures 35 to 42 are flowcharts illustrating the processing flow of the program that creates the judgment result DB 46. In the following explanation, the program described using Figures 35 to 42 will be referred to as the judgment program. The control unit 31 executes the judgment program as needed during periods of low load, such as late at night. Furthermore, the control unit 31 may execute the judgment program whenever the milestone DB 41, equipment list DB 42, logbook DB 43, implementation plan DB 44, or government agency DB 45 are updated.

[0156] The control unit 31 obtains the name of the site to be processed (step S621). For example, the control unit 31 obtains the site names recorded in the site name field of the milestone DB 41 one by one in order and then executes the subsequent processing.

[0157] The control unit 31 searches the milestone DB 41 using the site name as the key and selects one milestone record (step S622). If there are multiple milestone records corresponding to the site name obtained in step S621, the control unit 31 selects one corresponding milestone record and executes the subsequent processing.

[0158] The control unit 31 determines whether or not the actual date is recorded in the actual date field of the record selected in step S622 (step S623). If it determines that the actual date is recorded (YES in step S623), the control unit 31 records an "OFF" flag in the expired field of the record being processed (step S624). The control unit 31 also records an "OFF" flag in the near-expiration field of the record being processed (step S625).

[0159] If it is determined that the actual date is not recorded (NO in step S623), the control unit 31 determines whether the scheduled date recorded in the scheduled date field of the record being processed, i.e., the deadline for the milestone's execution, is approaching (step S631). Specifically, if the number of days until the scheduled date falls below a predetermined threshold, the control unit 31 determines that the deadline for the milestone's execution is approaching.

[0160] If it is determined that the deadline is approaching (YES in step S631), the control unit 31 records an "OFF" flag in the expired field of the record being processed (step S632). The control unit 31 then records an "ON" flag in the near-expiration field of the record being processed (step S633).

[0161] If it is determined that the deadline is not imminent (NO in step S631), the control unit 31 determines whether the scheduled date recorded in the scheduled date field of the record being processed, i.e., the deadline for the execution of the milestone, has already passed (step S634).

[0162] If it is determined that the deadline has passed (YES in step S634), the control unit 31 records an "ON" flag in the expired field of the record being processed (step S635). The control unit 31 records an "OFF" flag in the nearing expiration field of the record being processed (step S636).

[0163] If it is determined that the deadline has not passed (NO in step S634), the control unit 31 records an "OFF" flag in the expired field of the record being processed (step S637). The control unit 31 also records an "OFF" flag in the nearing expiration field of the record being processed (step S638).

[0164] After the completion of steps S625, S633, S636, or S638, the control unit 31 determines whether it has finished processing all milestone records corresponding to the site name obtained in step S621 (step S641). If it determines that it has not finished (NO in step S641), the control unit 31 returns to step S622.

[0165] If it is determined that the process has finished (YES in step S641), the control unit 31 records the number of milestone records corresponding to the site name obtained in step S621 that have the "ON" flag recorded in the expired field in the expired count field (step S642). The control unit 31 also records the number of milestone records corresponding to the site name obtained in step S621 that have the "ON" flag recorded in the nearing expiration field in the nearing expiration count field (step S643).

[0166] The control unit 31 searches the judgment result DB 46 using the site name as the key and extracts the judgment result field (step S644). The control unit 31 determines whether the value recorded in the expiration number field in step S642 is "0" or not (step S645).

[0167] If it is determined to be "0" (YES in step S645), the control unit 31 records an "OFF" flag in the expiration field of the determination record extracted in step S644 (step S646). If it is determined to be not "0" (NO in step S645), the control unit 31 records an "ON" flag in the expiration field of the determination record extracted in step S644 (step S647).

[0168] After step S646 or step S647 is completed, the control unit 31 determines whether the value recorded in the near-expiration field in step S643 is "0" (step S648).

[0169] If it is determined to be "0" (YES in step S648), the control unit 31 records an "OFF" flag in the near-expiration field of the determination record extracted in step S644 (step S649). If it is determined to be not "0" (NO in step S648), the control unit 31 records an "ON" flag in the near-expiration field of the determination record extracted in step S644 (step S650).

[0170] Steps S635 and S647 result in the display of a warning mark 511, which is a warning message, in the "My..." column, as explained using Figure 10, for any project where there are milestones that have not been completed by the scheduled date set in milestone DB41.

[0171] Furthermore, a column may be provided between the "My..." column and the "A Delivery" column in Figure 10 to indicate that the scheduled date set in Milestone DB41 is approaching, that is, that the near-deadline record in Judgment Result DB46 is "ON". If the expired record in Judgment Result DB46 is "OFF" and the near-deadline record is "ON", a mark indicating that it is a warning information may be displayed in the "My..." column as explained using Figure 10.

[0172] After step S649 or step S650 is completed, the control unit 31 searches the equipment list DB42 using the site name obtained in step S621 as the key and selects one equipment list record (step S661). If there are multiple equipment list records corresponding to the site name obtained in step S621, the control unit 31 selects one corresponding equipment list record and executes the subsequent processing.

[0173] The control unit 31 determines whether the order date is recorded in the order date field of the record selected in step S661 (step S662). If it determines that the order date is recorded (YES in step S662), the control unit 31 records an "OFF" flag in the order delay field of the record being processed (step S663). If it determines that the order date is not recorded (NO in step S662), the control unit 31 checks whether the order confirmation date is recorded in the order confirmation date field of the record being processed (step S664).

[0174] If it is determined that the order confirmation date is recorded (YES in step S664), the control unit 31 determines whether the order confirmation date has passed or not (step S665). If it is determined that the order confirmation date has passed or not (YES in step S665), or if it is determined that the order confirmation date is not recorded (NO in step S664), the control unit 31 records an "ON" flag in the order delay field of the record being processed (step S666). If it is determined that the order confirmation date has not passed or not (NO in step S665), the control unit 31 records an "OFF" flag in the order delay field of the record being processed (step S667).

[0175] As a result of the series of processes in steps S664, S665, and S666, if the order confirmation date has passed and the order confirmation date is not recorded, the control unit 31 records an "ON" flag in the order delay field. For construction projects in which there are equipment list records with an "ON" flag recorded in the order delay field as a result of the procedures described later, the first mark 511, which is warning information, is displayed in the "A Order" column as explained using Figure 10.

[0176] After the completion of step S663, step S666, or step S667, the control unit 31 determines whether or not the delivery date is recorded in the actual date field of the record being processed (step S671). If it determines that the delivery date is recorded (YES in step S671), the control unit 31 records an "OFF" flag in the delivery delay field of the record being processed (step S672).

[0177] If it is determined that the delivery date is not recorded (NO in step S671), the control unit 31 determines whether the scheduled delivery start date is recorded in the scheduled delivery start date field of the record being processed (step S673). If it is determined that the scheduled delivery start date is recorded (YES in step S673), the control unit 31 determines whether the scheduled delivery start date has already passed (step S674).

[0178] If it is determined that the scheduled delivery start date has passed (YES in step S674), or if it is determined that the scheduled delivery start date is not recorded (NO in step S673), the control unit 31 records an "ON" flag in the delivery delay field of the record being processed (step S675).

[0179] If it is determined that the scheduled delivery start date has not yet passed (NO in step S674), the control unit 31 determines whether the scheduled delivery start date is imminent (step S676). Here, whether the scheduled delivery start date is imminent is determined, for example, based on whether the number of days until the scheduled delivery start date is within a predetermined period. The predetermined period is, for example, the number of days entered in the pre-confirmation days field. In addition, an arbitrary threshold may be used to determine whether or not it is within the predetermined period.

[0180] If it is determined that the scheduled delivery start date is imminent (YES in step S676), the control unit 31 determines whether or not the acceptance date is recorded in the acceptance date field of the record being processed (step S677). If it is determined that the acceptance date is recorded (YES in step S677), or if it is determined that the scheduled delivery start date is not imminent (NO in step S676), the control unit 31 records an "OFF" flag in the delivery delay field of the record being processed (step S678). If it is determined that the acceptance date is not recorded (NO in step S677), the control unit 31 records an "ON" flag in the delivery delay field of the record being processed (step S675).

[0181] As a result of the series of processes in steps S674, S676, S677, and S675, if the scheduled delivery start date is within the predetermined period and the acceptance date is not recorded, or if the scheduled delivery start date has passed and the actual delivery start date is not recorded, the control unit 31 records an "ON" flag in the delivery delay field of the equipment list DB42.

[0182] After the completion of step S672, step S675, or step S678, the control unit 31 determines whether it has finished processing all equipment list records corresponding to the site name obtained in step S621 (step S679). If it determines that processing has not been completed (NO in step S679), the control unit 31 returns to step S661.

[0183] If the control unit determines that the process has ended (YES in step S679), it determines whether there is a record in the equipment list corresponding to the site name obtained in step S621 in which the "ON" flag is recorded in the delivery delay field (step S681). If it determines that such a record exists (YES in step S681), the control unit 31 records the "ON" flag in the A delivery field of the determination record extracted in step S644 (step S682). If it determines that such a record does not exist (NO in step S681), the control unit 31 records the "OFF" flag in the A delivery field of the determination record extracted in step S644 (step S683).

[0184] As a result of the processing in step S682, for construction projects where there is an equipment list record with the "ON" flag recorded in the delivery delay field, the first mark 511, which is warning information, will be displayed in the "A Delivery" column as explained using Figure 10.

[0185] After the completion of step S682 or step S683, the control unit 31 determines whether there is a record in the equipment list corresponding to the site name obtained in step S621 in which the order delay field has an "ON" flag recorded (step S684). If it is determined that such a record exists (YES in step S684), the control unit 31 records an "ON" flag in the A order field of the determination record extracted in step S644 (step S685). If it is determined that such a record does not exist (NO in step S684), the control unit 31 records an "OFF" flag in the A order field of the determination record extracted in step S644 (step S686).

[0186] As a result of the processing in step S685, for construction projects where there is an equipment list record with the "ON" flag recorded in the order delay field, the first mark 511, which is warning information, will be displayed in the "A Order" column as explained using Figure 10.

[0187] After step S685 or step S686 is completed, the control unit 31 obtains the project name corresponding to the site name obtained in step S621 (step S687). As mentioned above, the project name is associated with the site name by a DB (not shown in the diagram), and once the site name is determined, the project name is also uniquely determined. The control unit 31 searches the log DB 43 using the project name as the key and extracts all corresponding log records. The control unit 31 determines whether the extracted log records contain a record with "-" recorded in the file field, that is, a record indicating that the log has not been submitted despite the submission deadline having passed (step S688).

[0188] If it is determined that the record is recorded (YES in step S688), the control unit 31 records an "ON" flag in the log field of the determination record extracted in step S644 (step S689). If it is determined that the record is not recorded (NO in step S688), the control unit 31 records an "OFF" flag in the log field of the determination record extracted in step S644 (step S690).

[0189] As a result of the processing in step S689, for projects where there are unsubmitted logs despite the submission deadline having passed, a warning information, mark 511, will be displayed in the "Log" column as explained using Figure 10.

[0190] After step S689 or step S690 is completed, the control unit 31 searches the implementation plan DB 44 using the site name obtained in step S621 as the key and selects one implementation plan record (step S711). If there are multiple implementation plan records corresponding to the site name obtained in step S621, the control unit 31 selects one corresponding implementation plan record and executes the subsequent processing.

[0191] The control unit 31 obtains the start date from the start date field of the record being processed (step S712). The control unit 31 determines whether or not the start date falls within a predetermined period (step S713). The predetermined period is, for example, one month.

[0192] If it is determined that the period is within a predetermined timeframe (YES in step S713), the control unit 31 determines whether or not an approval date is recorded in the approval date field of the record being processed (step S714). If it is determined that an approval date is recorded (YES in step S714), the control unit 31 records an "OFF" flag in the execution field of the record being processed (step S715).

[0193] If it is determined that the approval date is not recorded (NO in step S714), the control unit 31 records an "ON" flag in the execution field of the record being processed (step S716). If it is determined that the start date is not within the predetermined period (NO in step S713), the control unit 31 records an "OFF" flag in the execution field of the record being processed (step S717).

[0194] After the completion of step S715, step S716, or step S717, the control unit 31 determines whether it has finished processing all implementation plan records corresponding to the site name obtained in step S621 (step S718). If it determines that processing has not been completed (NO in step S718), the control unit 31 returns to step S711.

[0195] If it is determined that the process has ended (YES in step S718), the control unit 31 determines whether there is a record in the implementation plan list corresponding to the site name obtained in step S621 in which the "ON" flag is recorded in the implementation field (step S719). If it is determined that such a record exists (YES in step S719), the control unit 31 records the "ON" flag in the implementation field of the determination record extracted in step S644 (step S720). If it is determined that such a record does not exist (NO in step S719), the control unit 31 records the "OFF" flag in the implementation field of the determination record extracted in step S644 (step S721).

[0196] As a result of the processing in step S716, for construction projects in which there are implementation plans with the "ON" flag recorded in the implementation field of the implementation plan DB44, the first mark 511, which is warning information, will be displayed in the "Implementation" column as explained using Figure 10.

[0197] After step S720 or step S721 is completed, the control unit 31 searches the government agency database 45 using the site name obtained in step S621 as the key and selects one government agency record (step S731). If there are multiple government agency records corresponding to the site name obtained in step S621, the control unit 31 selects one corresponding government agency record and executes the subsequent processing.

[0198] The control unit 31 determines whether the permission acceptance date is recorded in the permission acceptance date field of the record being processed (step S732). If it determines that the permission acceptance date is recorded (YES in step S732), the control unit 31 records the "OFF" flag in the document field of the record being processed (step S733).

[0199] If it is determined that the permit acceptance date is not recorded (NO in step S732), the control unit 31 determines whether or not the scheduled notification date is recorded in the scheduled notification date field of the record being processed (step S741). If it is determined that the scheduled notification date is not recorded (NO in step S741), the control unit 31 records an "ON" flag in the document field of the record being processed (step S742).

[0200] If it is determined that the scheduled notification date is recorded (YES in step S741), the control unit 31 determines whether the scheduled notification date has passed or not (step S743). If it is determined that the scheduled notification date has passed or not (YES in step S743), the control unit 31 records an "ON" flag in the document field of the record being processed (step S744).

[0201] The control unit 31 determines whether M days have elapsed since the scheduled notification date (step S745). M days is an estimate of the number of days required from the time the documents are submitted to the government office, etc. until permission is received, for example, 5 days. M days may be set to a different number of days depending on the type of documents to be submitted or the government office, etc. to which they are submitted. M days may be set arbitrarily by the site representative or the site representative's superior, etc.

[0202] If it is determined that M days have elapsed (YES in step S745), the control unit 31 determines whether N days have elapsed since the last overdue notification for the record being processed (step S746). Note that if step S746 is executed for the first time for a single record, the control unit 31 determines that N days have elapsed.

[0203] Here, an overdue notification is a notification informing that the deadline for a submission recorded in the submission field of a record being processed has been exceeded. N days is, for example, 30 days. N days may be set to a different number of days depending on the type of submission or the government agency to which it is submitted. N days may be set arbitrarily by the site representative or their supervisor.

[0204] If it is determined that N days have elapsed (YES in step S746), the control unit 31 sends an overdue notification (step S747). The overdue notification is sent to the site representative in charge via any means, such as email, SMS (Short Message Service), or automated voice call. The overdue notification may also be displayed on the display unit 25 of the information processing device 20 used by the site representative in charge via a pop-up screen or the like. In addition to the site representative in charge, the overdue notification may also be sent to the site representative's supervisor or other superior.

[0205] If the required documents have already been submitted to the government agency at the time of receiving the overdue notice, the site representative will inquire with the government agency about the situation and take necessary actions such as correcting the documents. If the required documents have not yet been submitted, the site representative will take necessary actions such as preparing and submitting the documents. The site representative will receive an overdue notice every N days until the permit is received. This prevents problems such as forgetting to obtain the necessary permits to proceed with the construction.

[0206] If it is determined that the scheduled submission date has not passed (NO in step S743), the control unit 31 records an "OFF" flag in the document field of the record being processed (step S751). The control unit 31 determines whether or not the date L days before the scheduled submission date has passed (step S752). L days is an estimate of the number of days required to prepare the submission documents, for example, 5 days. L days may be set to a different number of days depending on the type of submission document or the government office to which it is submitted. L days may be set arbitrarily by the site representative or the site representative's superior.

[0207] If it is determined that L days have passed (YES in step S752), the control unit 31 records an "ON" flag in the document field of the record being processed (step S753). The control unit 31 determines whether or not the schedule notification has been sent (step S754). The schedule notification is a notification informing the documents to be submitted and the scheduled submission date. If it is determined that it has not been sent (NO in step S754), the control unit 31 sends the schedule notification (step S755). The schedule notification may be sent to the site representative in charge, as well as to the site representative's superior, etc.

[0208] If, after the completion of steps S733, S755, S747, or S742, it is determined that M days have not elapsed (NO in step S745), that N days have not elapsed (NO in step S746), that L days ago has not elapsed (NO in step S752), or that the scheduled notification has been sent (YES in step S754), the control unit 31 determines whether it has finished processing all government records corresponding to the site name obtained in step S621 (step S756). If it is determined that processing has not been completed (NO in step S756), the control unit 31 returns to step S731.

[0209] If the control unit determines that the process has ended (YES in step S756), it determines whether there is a record among the government records corresponding to the site name obtained in step S621 in which the "ON" flag is recorded in the document field (step S761). If it determines that such a record exists (YES in step S761), the control unit 31 records the "ON" flag in the government field of the determination record extracted in step S644 (step S762). If it determines that such a record does not exist (NO in step S761), the control unit 31 records the "OFF" flag in the government field of the determination record extracted in step S644 (step S763).

[0210] As a result of the processing in step S762, for construction projects where the number of days until the scheduled notification date is within the prescribed period and the permit acceptance date is not recorded, and for construction projects where the scheduled notification date has passed and the permit acceptance date is not recorded, a warning information, mark 511, is displayed in the "Government" column as explained using Figure 10.

[0211] After step S762 or step S763 is completed, the control unit 31 determines whether or not it has finished processing all site names (step S764). If it determines that the processing is not finished (NO in step S764), the control unit 31 returns to step S621. If it determines that the processing is finished (YES in step S764), the control unit 31 terminates the processing.

[0212] According to this embodiment, information regarding the progress of the construction can be provided to the site manager and other relevant parties.

[0213] For example, the supervisor of the site representative and staff in the support department can quickly identify the presence of a priority monitoring item that is in a warning state by the first mark 511 displayed on the screen as explained using Figures 9 and 10. Therefore, even if the site representative is unable to proactively request support, necessary support can be provided in a push-type manner.

[0214] The timing at which the control unit 31 sends a notification is not limited to steps S755 and S747. For example, the control unit 31 may send a notification to the site representative, etc., when a flag recorded in the judgment result DB 46 changes from the "OFF" state to the "ON" state. The control unit 31 may also send a notification to the site representative, etc., when an expired flag or an approaching expiration flag recorded in the milestone DB 41 changes from the "OFF" state to the "ON" state.

[0215] The control unit 31 may send a notification to the site representative, etc., when the order delay flag or delivery delay flag recorded in the equipment list DB 42 changes from the "OFF" state to the "ON" state. The control unit 31 may also send a notification to the site representative, etc., when the implementation flag recorded in the implementation plan DB 44 changes from the "OFF" state to the "ON" state.

[0216] [Embodiment 2] Figure 43 is an explanatory diagram illustrating the configuration of the construction support system 10 of Embodiment 2. This embodiment relates to a configuration in which the construction support system 10 is realized by operating a general-purpose server computer 90 in combination with a program 97. Parts common to Embodiment 1 will not be explained.

[0217] The server computer 90 includes the aforementioned control unit 31, main memory 32, auxiliary memory 33, communication unit 34, and bus, as well as a reading unit 37.

[0218] Program 97 is recorded on a portable recording medium 96. The control unit 31 reads Program 97 via the reading unit 37 and saves it to the auxiliary storage device 33. The control unit 31 may also read Program 97 stored in a semiconductor memory 98, such as flash memory, installed in the server computer 90. Furthermore, the control unit 31 may download Program 97 from a computer (not shown) connected via the communication unit 34 and a network and save it to the auxiliary storage device 33.

[0219] Program 97 is installed as a control program for the server computer 90, loaded into the main memory 32, and executed. The control unit 31 transmits the portion of Program 97 that will be executed by the control unit 21 to each information processing device 20 via the network. The transmitted program is installed as a control program for the information processing device 20, loaded into the control unit 21, and executed. The control unit 21 may also download Program 97 from a computer (not shown) connected via the network and save it to the auxiliary storage device 23. Thus, the construction support system 10 described in Embodiment 1 is realized.

[0220] The program is an example of a program product. The program may be provided on a recording medium or distributed from an external computer. Computer programs can be deployed to run on a single computer, at a single site, or distributed across multiple sites and interconnected by a communication network.

[0221] The technical features (constituent elements) described in each embodiment are combinable with each other, and by combining them, new technical features can be formed. The embodiments disclosed herein should be considered in all respects to be illustrative and not restrictive. The scope of the present invention is indicated by the claims, not in the sense described above, and all modifications within the sense and scope equivalent to the claims are intended to be included.

[0222] The independent and dependent claims described in the claims can be combined with each other in any combination, regardless of the form of reference. Furthermore, while the claims use a multi-claim format in which claims refer to two or more other claims (multi-claim format), this is not the only option. Claims may also be described using a multi-claim format in which at least one multi-claim is referenced (multi-multi-claim format). [Explanation of symbols]

[0223] 10. Construction support system 20 Information Processing Devices 21 Control Unit 22 Main storage 23 Auxiliary storage device 24 Communications Department 30 servers 31 Control Unit 32 Main storage 33 Auxiliary storage device 34 Communications Department 41 Milestone DB 42 Equipment List Database 43 Journal DB 44 Implementation Plan Database 45 Government Agency Databases 46 Judgment result DB 511 Mark 1 512 Mark 2 61 Construction List Section 62 Milestone section 63 Schedule column 64 Basic site information column 65. Section for documents to be made public at the site. 66 Search Criteria Field 67 Notices Section 681 Expired items column 682 Number of items nearing their deadline 71. Construction Project Name Column 96 Portable recording media 97 Programs 98 Semiconductor memory

Claims

1. Multiple construction identification information for the construction projects to be managed is displayed in the first direction. Multiple monitoring items, including milestones indicating key management items, equipment delivery, and equipment ordering, are displayed in a second direction. When the monitoring item of the construction identification information satisfies the predetermined warning conditions, warning information is displayed at the corresponding position within the grid-like frame formed by the first and second directions. An information processing method in which a computer performs the processing.

2. The aforementioned monitoring items include milestones, equipment deliveries, equipment orders, as well as logs, implementation plans, and government notifications. The information processing method according to claim 1.

3. If the scheduled date set for the milestone has been exceeded, the warning information will be displayed. The information processing method according to claim 2.

4. The items relating to the delivery of the aforementioned equipment include information regarding the scheduled start date of delivery of the equipment, the date of customer acceptance of the equipment, and the actual start date of delivery of the equipment. The warning information is displayed if the scheduled delivery start date is within the specified period and the acceptance date is not recorded, or if the scheduled delivery start date has passed and the actual delivery start date is not recorded. The information processing method according to claim 1.

5. The items relating to the ordering of the aforementioned equipment include information regarding the order confirmation date for the aforementioned equipment, The warning information is displayed when the aforementioned order confirmation date has passed and the aforementioned order confirmation date is not recorded. The information processing method according to claim 1.

6. The warning information will be displayed if the logbook is not submitted within the specified deadline. The information processing method according to claim 2.

7. The warning information will be displayed if the aforementioned implementation plan is not submitted or approved within the specified deadline. The information processing method according to claim 2.

8. The items related to the aforementioned notification to the government include information regarding the planned date of notification to the government and the date of acceptance of permission. The warning information is displayed if the number of days until the scheduled notification date is within the prescribed period and the date of approval is not recorded, or if the scheduled notification date has passed and the date of approval is not recorded. The information processing method according to claim 2.

9. When input is received regarding the warning information for the aforementioned milestone, the following will be displayed: basic site information, the number of milestones subject to warnings, and the name, scheduled date, and status of each milestone. The information processing method according to any one of claims 1 to 8.

10. Multiple construction identification information for the construction projects to be managed is displayed in the first direction. Multiple monitoring items, including milestones indicating key management items, equipment delivery, and equipment ordering, are displayed in a second direction. When the monitoring item of the construction identification information satisfies the predetermined warning conditions, warning information is displayed at the corresponding position within the grid-like frame formed by the first and second directions. A program that instructs a computer to perform a process.

11. An information processing device comprising a control unit, The control unit, Multiple construction identification information for the construction projects to be managed is displayed in the first direction. Multiple monitoring items, including milestones indicating key management items, equipment delivery, and equipment ordering, are displayed in a second direction. When the monitoring item of the construction identification information satisfies the predetermined warning conditions, warning information is displayed at the corresponding position within the grid-like frame formed by the first and second directions. Information processing device.

Images