Information processing method, program, and information processor

Abstract

To provide an information processing method and the like that enable a person who has input an evaluation result during a patrol of a construction site to easily check the evaluation result.SOLUTION: An information processing method causes a computer 30 to execute processing of outputting a plurality of check matters for each of a plurality of check items related to electrical facility construction, receiving a user's response to each of the output check matters, storing checklist data in which the received responses, first identification information assigned to the user, and second identification information related to the electrical facility construction are associated with each other, displaying, from a plurality of stored checklist data, a list of checklist data stored in association with the first identification information assigned to a user in operation and the second identification information, accepting selection of checklist data to be edited, and outputting each check matter included in the checklist data whose selection has been accepted and a response to the check matter.SELECTED DRAWING: Figure 1

Description

[Technical Field]

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

[0002] A support system has been proposed to assist patrol workers in checking that gas-related construction work is being carried out properly (Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 7393294 Summary of the Invention [Problem to be solved by the invention]

[0004] In the patrol system of Patent Document 1, patrol members move to construction sites assigned by the system and repeatedly input their evaluations into checklists sent from the system. The evaluation results are promptly sent to the server.

[0005] However, the support system of Patent Document 1 does not provide a function that allows the person who inputs the evaluation results to easily recheck the evaluation results that have already been input.

[0006] In one aspect, the present invention aims to provide an information processing method that allows the person who inputs the evaluation results during a construction site patrol to easily check them. [Means for solving the problem]

[0007] The information processing method involves a computer executing a process in which it outputs multiple confirmation items for each of multiple confirmation items related to electrical equipment construction, accepts a user's response to each of the output confirmation items, stores checklist data that associates the accepted response with first identification information assigned to the user and second identification information related to the electrical equipment construction, displays a list of the stored checklist data stored in association with the first identification information assigned to the user currently operating the device and the second identification information, accepts a selection of checklist data to be edited, and outputs each confirmation item included in the checklist data whose selection was accepted and the response to the confirmation item. [Effects of the Invention]

[0008] In one aspect, it is possible to provide an information processing method etc. that allows the person who inputs the evaluation results when patrolling a construction site to easily check them himself. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 is an explanatory diagram illustrating an overview of safety patrol operations. [Figure 2] FIG. 1 is an explanatory diagram illustrating a configuration of an information processing system. [Figure 3] FIG. 10 is an explanatory diagram illustrating the configuration of a checklist. [Figure 4] FIG. 10 is an explanatory diagram illustrating the record layout of a user DB. [Figure 5] FIG. 10 is an explanatory diagram illustrating the record layout of a checklist DB. [Figure 6] FIG. 10 is an explanatory diagram illustrating screen transitions. [Figure 7] FIG. 10 is an explanatory diagram illustrating screen transitions. [Figure 8] This is an example screen. [Figure 9] This is an example screen. [Figure 10] This is an example screen. [Figure 11] This is an example screen. [Figure 12]This is an example screen. [Figure 13] This is an example screen. [Figure 14] This is an example screen. [Figure 15] This is an example screen. [Figure 16] This is an example screen. [Figure 17] 10 is a flowchart illustrating the flow of processing of a program. [Figure 18] 10 is a flowchart illustrating the flow of processing of a program. [Figure 19] FIG. 10 is an explanatory diagram illustrating an example of utilization of data recorded in a checklist DB. [Figure 20] FIG. 10 is an explanatory diagram illustrating an example of utilization of data recorded in a checklist DB. [Figure 21] FIG. 10 is an explanatory diagram illustrating the configuration of an information processing system according to a second embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0010] [Embodiment 1] Electrical installation work involves the installation of electrical equipment such as power lines, distribution panels, lighting equipment, and power equipment in a variety of locations. Electrical installation work is often carried out in special locations, such as unfinished buildings, underground conduits, and on top of utility poles. Furthermore, electrical installation work involves tasks not typically performed in other occupations, such as live-line installation, which involves handling high-voltage powered wires. Therefore, even minor operational errors pose a risk of serious personal injury.

[0011] For example, large construction sites are legally required to appoint a general safety and health officer and to conduct safety patrols of the work site every day. During these safety patrols, a person stationed at the construction site checks the safety status of the entire construction site and takes corrective action if necessary.

[0012] However, with such patrols covering the entire construction site, the checklists used during patrols may not adequately reflect the specific precautions for electrical equipment construction.In addition, since patrol personnel are not necessarily familiar with electrical equipment construction, they may not be able to accurately evaluate items even if they are listed on the checklist.

[0013] Therefore, electrical equipment construction companies that have been contracted to carry out electrical equipment construction work may conduct their own safety patrols at the electrical equipment construction site. These safety patrols are carried out by auditors with sufficient expertise, such as managers working at the head office, who are not normally stationed at the patrol site.

[0014] Preventing accidents during electrical equipment construction through safety patrols protects the right to work of all people working on electrical equipment construction sites and contributes to creating an environment where people can work safely and with peace of mind.

[0015] Preventing accidents during electrical installation work also has the effect of preventing delays and rising costs in construction and infrastructure work, etc. For example, ensuring that construction work on apartment complexes and other housing complexes proceeds smoothly contributes to ensuring that everyone can live in affordable, safe, and adequate housing.

[0016] For example, ensuring that construction of electricity infrastructure progresses smoothly will ensure that everyone has access to affordable, stable, and modern energy, and will contribute to the creation of high-quality, reliable, sustainable, and disaster-resistant infrastructure.

[0017] Inspectors at electrical installation companies have many tasks in addition to safety patrols. On patrol days, they visit several construction sites, filling out checklists at each site and providing feedback to the workers. In this embodiment, an information processing system 10 is described that supports safety patrols by electrical installation company inspectors and improves work efficiency.

[0018] FIG. 1 is an explanatory diagram outlining the safety patrol work. An auditor visits an electrical equipment construction site carrying an information processing device 30 such as a smartphone or tablet. While patrolling the site, the auditor inputs the evaluation results into a checklist 43 displayed on a touch panel 35 (see FIG. 2) of the information processing device 30. The auditor provides feedback on the patrol results to the site manager, pointing out good points and offering advice on areas requiring improvement.

[0019] The checklist 43 is sent to the server 20 via the network and stored in the checklist DB 42 (see Figure 2). By appropriately analyzing the stored data, it is possible to compile a report on the status of the electrical work site, such as identifying items where many sites are not performing the work according to the checklist 43. The report can be used to plan measures such as reviewing work procedures.

[0020] For example, an auditor may spend a whole day conducting safety patrols at several electrical equipment construction sites. The checklists 43 filled out at each electrical equipment construction site are sent to the checklist database 42 as needed, and can be viewed by users with access rights. Therefore, after the safety patrol is over, there is no need for additional desk work, such as returning to the office and organizing and submitting the checklists 43.

[0021] The inspector can add or revise the checklist 43 while traveling on public transport, for example. The results of the additions and revisions are promptly reflected in the checklist DB 42. In other words, the inspector can add special notes, such as points that he or she noticed or points of concern, to the checklist 43 while the electrical equipment construction site is still fresh in his or her memory.

[0022] 2 is an explanatory diagram illustrating the configuration of the information processing system 10. The information processing system 10 includes a server 20 and a plurality of information processing devices 30. The server 20 and the information processing devices 30 are capable of communicating with each other via a network.

[0023] The server 20 includes a control unit 21, a main storage device 22, an auxiliary storage device 23, a communication unit 24, and a bus. The control unit 21 is an arithmetic and control device that executes the program of this embodiment. The control unit 21 uses one or more central processing units (CPUs), graphics processing units (GPUs), multi-core CPUs, or the like. The control unit 21 is connected to each hardware unit that constitutes the server 20 via the bus.

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

[0025] The auxiliary storage device 23 is a storage device such as an SRAM, a flash memory, a hard disk, or a magnetic tape. A user DB (Database) 41, a checklist DB 42, programs to be executed by the control unit 21, and various data required for executing the programs are stored in the auxiliary storage device 23. The user DB 41 and the checklist DB 42 may be stored in an external mass storage device connected to the server 20.

[0026] The communication unit 24 is an interface for communication between the server 20 and a network or other devices.

[0027] The server 20 is a mainframe computer, a virtual machine running on a mainframe computer, a plurality of personal computers performing distributed processing, or a cloud computing system. The server 20 may also be an information device such as a general-purpose personal computer or a tablet.

[0028] The information processing device 30 includes a control unit 31, a main memory device 32, an auxiliary memory device 33, a communication unit 34, a touch panel 35, a camera 37, a GPS (Global Positioning System) 38, and a bus. The touch panel 35 includes an input unit 351 and a display unit 352.

[0029] The control unit 31 is an arithmetic and control device that executes the program of this embodiment. The control unit 31 uses one or more CPUs, GPUs, multi-core CPUs, etc. The control unit 31 is connected to each hardware unit that constitutes the information processing device 30 via a bus.

[0030] The main memory device 32 is a memory device such as an SRAM, a DRAM, a flash memory, etc. The main memory device 32 temporarily stores information required during processing performed by the control unit 31 and programs being executed by the control unit 31.

[0031] The auxiliary storage device 33 is a storage device such as an SRAM, a flash memory, a hard disk, a magnetic tape, etc. The auxiliary storage device 33 stores programs to be executed by the control unit 31 and various data required for executing the programs.

[0032] The communication unit 34 is an interface for communication between the information processing device 30 and a network or other devices. The display unit 352 is, for example, a liquid crystal display panel or an organic EL (electro-luminescence) panel. The input unit 351 is stacked on the display unit 352. The information processing device 30 may include the display unit 352 and the input unit 351 such as a mouse. The information processing device 30 may also include a microphone and a speaker, which are interfaces for audio input and output.

[0033] The camera 37 may be hardware separate from the information processing device 30. The GPS 38 performs positioning based on radio waves from positioning information satellites and radio waves from base stations, and outputs positioning information indicating the position of the information processing device 30. Note that although the present embodiment uses the term GPS, the positioning information satellite is not limited to the US GPS satellite. For example, any positioning information satellite, such as the Quasi-Zenith Satellite Michibiki, may be used.

[0034] The information processing device 30 is a general-purpose portable information device such as a smartphone or tablet carried by each of the parties. The information processing device 30 may be a general-purpose information device such as a laptop or desktop computer. The information processing device 30 may also be dedicated hardware manufactured for the information processing system 10 of this embodiment.

[0035] 3 is an explanatory diagram illustrating the configuration of the checklist 43. The checklist 43 of this embodiment is configured in three layers: field, check items, and check matters. In addition to the "construction work" shown in FIG. 3, the field includes items that indicate broad classifications of electrical equipment work, such as "power distribution work" and "information and communication work."

[0036] Verification items are items that categorize the content that should be checked by field. Verification items are each item that an auditor should check at an electrical equipment construction site. As a rule, for each verification item, the auditor is required to select one of three options: "Good," "Bad," or "Not applicable." However, the items "Points of Advice and Guidance - Good Examples," "Improvements," and "Special Notes" shown at the bottom of Figure 3 accept text input by the user. The "Attached Files" item can accept up to 10 attached files, for example.

[0037] For example, the check items included in the check items for "1. Basic safety management" shown in Figure 3 are common to all fields. Check items such as "2. Electric shock" and "3. Falls" and the check items included in each check item are determined appropriately for each field.

[0038] 4 is an explanatory diagram illustrating the record layout of the user DB 41. The user DB 41 is a DB that records users who have access rights to the checklist DB 42. The user DB 41 has a user ID (identifier) ​​field, a name field, and a field field.

[0039] The user ID field records a user ID that is uniquely assigned to each user. The name field records the user's name. The field field records the user's field of expertise. The user DB 41 has one record for each user.

[0040] 5 is an explanatory diagram illustrating the record layout of the checklist DB 42. As described above, the checklist DB 42 is a DB that stores checklists 43 filled out by individual auditors.

[0041] The checklist DB 42 has fields corresponding to each item included in the checklist 43. Specifically, the checklist DB 42 has a field, a bibliographic information field, and a checklist field. The bibliographic information field has fields related to the bibliographic information of the checklist 43, such as a title field, an implementation date field, an implementer field, and a construction project name field. The implementer field has a name field and a user ID field.

[0042] The checklist field has fields corresponding to each check item in the checklist 43 defined for each field. The fields corresponding to each check item in the checklist 43 include the fields corresponding to each check item described using FIG. 3, a field for points of advice and good practices, a field for improvement details, a field for special notes, and a field for attached files.

[0043] The field field records the broad classification of electrical equipment construction work. Each subfield of the bibliographic information field records the bibliographic information of the checklist 43. The fields corresponding to each confirmation item of the checklist 43 record the results of the user's response to each confirmation item.

[0044] The Good Practices, Improvements, and Special Notes fields record user comments about electrical equipment construction work. The Attachment field records attachments specified by the user. The checklist DB 42 has one record for each checklist 43.

[0045] 6 and 7 are explanatory diagrams illustrating screen transitions. Specific examples of each screen will be described later. When a user operates information processing device 30 to start the program of this embodiment, control unit 31 displays top page 51 on touch panel 35. Top page 51 displays new input button 61 and edit button 62. Using FIG. 6, we will explain the screen transitions when new input button 61 is selected on top page 51.

[0046] When the control unit 31 receives selection of the new input button 61 on the top page 51, it transitions to a mode in which it receives input for the newly generated checklist 43. The control unit 31 displays the bibliographic information page 52 on the touch panel 35. The bibliographic information page 52 displays a cancel button 63 and a next page button 64. When the control unit 31 receives selection of the cancel button 63, it ends the processing.

[0047] When the control unit 31 receives the selection of the next page button 64, it displays the checklist page 53 on the touch panel 35. The checklist page 53 displays a next page button 64, a previous page button 65, and a checklist 43. The checklist 43 is divided into multiple pages, each of which contains multiple check items. The user inputs the check items displayed on the touch panel 35 as appropriate.

[0048] When the control unit 31 receives the selection of the previous page button 65, it saves the checklist 43 that the user is inputting and displays the previous checklist page 53 on the touch panel 35. When the control unit 31 receives the selection of the next page button 64, it determines whether the next page is the final page of the checklist 43.

[0049] If it is determined that the next page is not the final page, the control unit 31 saves the checklist 43 that the user is inputting and displays the next checklist page 53 on the touch panel 35. If it is determined that the next page is the final page, the control unit 31 displays the final checklist page 535 on the touch panel 35.

[0050] The final checklist page 535 displays a previous page button 65 and a save and finish button 66. When the selection of the save and finish button 66 is accepted, the control unit 31 saves the checklist 43 that the user is entering and then ends the processing. When the selection of the previous page button 65 is accepted, the control unit 31 saves the checklist 43 that the user is entering and displays the previous checklist page 53 on the touch panel 35.

[0051] The screen transition when the edit button 62 is selected on the top page 51 will be described with reference to FIG.

[0052] When the control unit 31 receives the selection of the edit button 62 on the top page 51, the control unit 31 transitions to a mode in which editing of a previously saved checklist 43 is received. The control unit 31 displays an input history page 56 on the touch panel 35.

[0053] The input history page 56 displays a list of the input history of the checklist 43 of the current user, a top button 67, and a new button 68. When the control unit 31 receives selection of the new button 68, it transitions to new input mode. Specifically, the control unit 31 creates a new checklist 43 and displays the bibliographic information page 52 described with reference to FIG. 6. When the control unit 31 receives input from the top button 67, it displays the top page 51 on the touch panel 35.

[0054] When the selection of an input history is accepted from the list of input histories, the control unit 31 displays the bibliographic information page 52 of the checklist 43 corresponding to the selected input history in the browsing mode on the touch panel 35. A previous page button 65, a delete button 71, and an edit button 72 are displayed on the bibliographic information page 52 in the browsing mode.

[0055] When the control unit 31 receives the selection of the previous page button 65, it displays the input history page 56 on the touch panel 35. When the control unit 31 receives the selection of the delete button 71, it deletes the checklist 43 being displayed on the input history page 56 and returns to the input history page 56. When the control unit 31 receives the selection of the edit button 72, it switches the displayed bibliographic information page 52 to edit mode. The subsequent processing is the same as that for the bibliographic information page 52 described using FIG. 6.

[0056] That is, the control unit 31 accepts the selection of the input history from the input history page 56 and displays the bibliographic information page 52, and then accepts the selection of the edit button 72, thereby accepting the selection of the checklist 43 to be edited.

[0057] 8 to 16 are examples of screens. Fig. 8 shows an example of a screen of the top page 51 displayed on the information processing device 30 used by the user in charge of construction work. The area of ​​responsibility of each user is recorded in the area field in the user DB 41 described using Fig. 4.

[0058] At the top of the top page 51, "Safety Check Sheet (Construction Work)" is displayed. Below that, safety goals are displayed in large letters. The goals are set, for example, for each month or season, and are distributed from the control unit 21 to each information processing device 30. The user can naturally check the goals each time they start the program. At the bottom of the screen, a new input button 61 and an edit button 62 are displayed.

[0059] FIG. 9 shows an example of a bibliographic information page 52. A cancel button 63 is displayed in the upper left of the screen, and a next page button 64 is displayed in the lower right. Below the cancel button 63, the screen is arranged with a title field 811, an implementation date field 812, a weather field 813, a field implementer field 814, a construction project name field 815, and a work content field 816. When the user scrolls the screen up, a field for the site agent, a field for the name of the cooperating company, and a field for the person in charge of the work are displayed. The positions of the cancel button 63 and the next page button 64 are not affected by the scroll. A scroll bar may be displayed on the right edge of the screen.

[0060] The date and time when the checklist 43 was newly created is automatically entered in the title field 811. The user can edit the title field 811 as needed. The date when the checklist 43 was created is automatically entered in the implementation date field 812. If the checklist 43 was newly created on a day other than the audit implementation date, the user can edit the implementation date field 812 as needed.

[0061] 9, the weather field 813 is blank. The user inputs the weather for the time period during which the audit was conducted into the weather field 813. For example, when the user performs a specific operation such as a triple tap, the control unit 31 may obtain the weather for the current location from a weather information website and automatically input the weather information into the weather field 813.

[0062] The name, user ID, etc. of the user using the information processing device 30 are automatically entered in the implementer column 814. The user appropriately enters the name of the construction project at the site to be inspected and the details of the work to be done on that day in the construction project name column 815 and the work details column 816. The control unit 31 may acquire a construction plan from the process management server of the electrical equipment construction company and automatically enter information into the construction project name column 815 and the work details column 816.

[0063] The user name and user ID entered in the inspector column 814 are examples of first identification information assigned to the user operating the information processing device 30. The construction project name entered in the construction project name column 815 is an example of second identification information related to power facility construction. The second identification information may include the date the audit was conducted, entered in the construction date column 812, and the construction project name, entered in the inspector column 814. Data related to one checklist 43 is an example of checklist data in which the first identification information and the second identification information are associated.

[0064] FIG. 10 shows an example of a checklist page 53. A check box 821 is displayed below each confirmation item in the checklist 43. The check box 821 is a pull-down menu button, and the user can select and enter one of "Good," "Bad," or "Not Applicable." The user's operation of the pull-down menu is an example of the user's response to each confirmation item included in the checklist 43. In other words, the control unit 31 accepts the user's response via the pull-down menu. In FIG. 10, none of the check boxes 821 are filled in. The checklist page 53 is also scrollable.

[0065] In Figure 10, for the confirmation items "2-1" and "2-5," a "◎" is displayed immediately after the number. As is clear from the display in the center of the top page 51 shown in Figure 8 that "◎ indicates a key item," confirmation items marked with a "◎" are items that auditors should pay particular attention to.

[0066] The control unit 31 displays "◎" for check items that are determined to be particularly important for ensuring safety at the construction site. The check items for which "◎" is displayed may be changed as appropriate in accordance with the targets displayed on the top page 51. In such a case, information regarding the check items for which "◎" is displayed along with the targets is also distributed from the control unit 21 to each information processing device 30.

[0067] Instead of displaying "◎", the control unit 31 may display the text color of the important check items in a more eye-catching color or font than other check items. By displaying important check items and other check items in different ways, it is possible to provide an information processing system 10 that draws the auditor's attention to important items.

[0068] 11 and 12 show examples of a final checklist page 535. When the user scrolls upward on the screen of Fig. 11, the screen of Fig. 12 is displayed. As shown in Fig. 11, on the final checklist page 535 during scrolling, a previous page button 65 is displayed in the upper left of the screen, and a save end button 66 is displayed in the upper right of the screen.

[0069] 12 shows the last part of the final checklist page 535. The last part of the final checklist page 535 has a comments field 831, an improvement content field 832, a special notes field 833, and an attachment field 834, and a previous page button 65 is displayed in the upper right corner of the screen. The user enters text into the comments field 831, the improvement content field 832, and the special notes field 833. The comments field 831, the improvement content field 832, and the special notes field 833 are examples of input fields that accept text input of comments regarding electrical equipment construction work.

[0070] The user specifies data stored in the auxiliary storage device 33, such as photographs taken at the construction site and audio data recorded, and attaches it to the attachment field 834. The attachment field 834 is an example of an input field that accepts input of comments about electrical equipment construction work by audio or the like.

[0071] 6, when the control unit 31 accepts the selection of the save and finish button 66, the control unit 31 ends the processing after saving the checklist 43 that the user is entering. In other words, the save and finish button 66 is a button that accepts instructions to end the acceptance of the user's responses to each confirmation item included in the checklist 43 and to save the checklist 43.

[0072] 13 is an example of an input history page 56. Arranged from left to right at the top of the input history page 56 are a top button 67, a reload button 73, a sort button 74, and a new button 68. Below these buttons, a search field 841 is arranged. Below the search field 841, history fields 842 are arranged in a vertical row. Each history field 842 has a title field 843, a date field 844, and a weather field 845 arranged therein.

[0073] The title field 843, date field 844, and weather field 845 display information entered via the title field 811, work date field 812, and weather field 813 of the bibliographic information page 52 described with reference to Figure 9. The history field 842 may be provided with fields for displaying information entered via, for example, the person who carried out the work field 814, the project name field 815, or the work content field 816.

[0074] As described above, input history page 56 displays a list of input histories related to checklists 43 entered by the user currently using information processing device 30. Each history column 842 shows one checklist 43 entered by an auditor.

[0075] In other words, the input history page 56 is an example of a screen that selectively displays a list of checklist data that associates first identification information assigned to individual users with second identification information related to the electrical equipment construction work being audited, and that is stored in association with the first identification information assigned to the user currently using the information processing device 30.

[0076] For example, if the construction project name entered via the construction project name field 815 is displayed below the weather field 845, the input history page 56 is an example of a screen that displays a selectable list of second identification information including the date displayed in the date field 844 and the construction project name.

[0077] When the user selects the reload button 73, the control unit 31 obtains the latest information from the checklist DB 42 via the network and updates the input history page 56. When the user selects the sort button 74, the arrangement order of the history column 842 switches between ascending order and descending order. When the user selects the sort button 74, a screen for accepting settings of sorting conditions, such as key items to be sorted, may be displayed.

[0078] When the user scrolls the screen up or down, the multiple history fields 842 scroll up or down. The area above the search field 841 is not affected by the scrolling. A scroll bar may be displayed on the right edge of the screen.

[0079] By inputting a keyword into the search field 841 and instructing a search, the user can display on the input history page 56 the history field 842 relating to checklists 43 other than those for which the user is responsible.

[0080] FIG. 14 is an example of a bibliographic information page 52 in the browse mode. From left to right, a previous page button 65, a delete button 71, and an edit button 72 are displayed at the top of the bibliographic information page 52. An input checklist 43 is displayed on the bibliographic information page 52. When the user scrolls the screen up or down, the checklist 43 is scrolled. The user can check the contents of the input checklist 43 without worrying about accidentally editing the checklist 43.

[0081] 7, when the control unit 31 receives a user selection of the edit button 72, it switches the bibliographic information page 52 to the edit mode. In the edit mode, the user can edit each confirmation item in the checklist 43 as appropriate.

[0082] 15 is an example of a checklist list page 57. The checklist list page 57 is a screen displayed on the display unit 352 of the information processing device 30 used by a user in charge of analyzing checklists 43, for example, in the office of an electrical equipment construction company. The checklists 43 filled out by multiple auditors are displayed in a list. The user can appropriately set the items to be displayed on the screen and the extraction conditions for extracting the checklists 43 to be displayed on the screen.

[0083] A screen of spreadsheet software or database software may be used instead of the checklist list page 57. The user can use various functions of the spreadsheet software or database software to perform analysis such as extracting and graphing the data stored in the checklist DB 42.

[0084] 16 is an example of the shared team list screen 55. The shared team list screen 55 is a screen displayed on the display unit 352 of the information processing device 30 used by a user in charge of planning audit schedules, for example, in the office of an electrical equipment construction company. The shared team list screen 55 displays an add member button 75 and a list of members belonging to a team that shares information about the checklists 43 recorded in the checklist DB 42.

[0085] The user can register and delete members to the shared team by operating the add member button 75. For example, if the user uses the search field 841 described using Figure 13, checklists 43 that contain the keywords entered in the search field 841 are extracted from among the checklists 43 created by members belonging to the same shared team.

[0086] 17 and 18 are flowcharts illustrating the flow of program processing. The programs in FIGS. 17 and 18 are started when a user instruction to start the programs is received, such as by tapping an icon displayed on the touch panel 35. The control unit 31 performs user authentication (step S500). The user authentication may be performed by any method, such as biometric authentication, such as face authentication or fingerprint authentication, or by inputting a user ID and password. The control unit 31 may read information related to user authentication from the auxiliary storage device 33 and perform user authentication.

[0087] Although not shown in the flowchart, if the user authentication does not end normally, the control unit 31 ends the process. The control unit 31 may send a notification to the server 20 regarding the possibility of unauthorized access.

[0088] The control unit 31 determines the user's area of ​​responsibility (step S501). Specifically, the control unit 31 searches the user DB 41 using the user ID of the user authenticated in step S500 as a key to extract a record. The control unit 31 determines that the area recorded in the area field of the extracted record is the user's area of ​​responsibility.

[0089] The control unit 31 displays the top page 51 corresponding to the determined field on the touch panel 35 and waits for selection of the new input button 61 or the edit button 62 (step S502). The control unit 31 determines whether selection of the new input button 61 has been accepted (step S503).

[0090] If it is determined that selection of the new input button 61 has been accepted (YES in step S503), the control unit 31 enters a mode for newly inputting the checklist 43 (step S504). As explained using FIGS. 6 and 9, the control unit 31 displays the bibliographic information page 52 and accepts input from the user (step S505). If the user inputs a change instruction for an item that has already been entered, the control unit 31 corrects the checklist 43 based on the accepted change instruction. Details of the subsequent screen transitions will not be explained using flowcharts.

[0091] The control unit 31 accepts the user's editing of the checklist 43. The control unit 31 determines whether or not selection of the next page button 64, previous page button 65, or save end button 66, which instructs saving the checklist 43, has been accepted (step S506). If it is determined that selection of a button instructing saving has been accepted (YES in step S506), the control unit 31 saves the checklist 43 being processed in the auxiliary storage device 33 (step S507).

[0092] The control unit 31 transmits the checklist 43 stored in the auxiliary storage device 33 to the server 20 as needed. The control unit 31 may transmit the checklist 43 to the server 20 when the program ends. The electronic data of the checklist 43 transmitted from the control unit 31 to the server 20 is an example of checklist data.

[0093] The control unit 21 records the received checklist 43 in the checklist DB 42. Specifically, if the save instruction is the first time, the control unit 21 creates a new record in the checklist DB 42 and saves the items written in the received checklist 43 in the corresponding fields. If the save instruction is the second or subsequent time, the server 20 updates the corresponding record in the checklist DB 42 and saves it.

[0094] After step S507 is completed, or if it is determined that the selection of the button to instruct saving the checklist 43 has not been accepted (NO in step S506), the control unit 31 determines whether the selection of the button to instruct termination has been accepted (step S508). Specifically, the control unit 31 determines whether input from the cancel button 63 has been accepted.

[0095] If it is determined that the request has not been accepted (NO in step S508), the control unit 31 returns to step S505. If it is determined that the request has been accepted (YES in step S508), the control unit 31 ends the process.

[0096] If it is determined that selection of the new input button 61 has not been accepted (NO in step S503), the control unit 31 acquires the input history of the checklist 43 (step S511). Specifically, for example, the control unit 31 acquires the input history recorded in the auxiliary storage device 33.

[0097] The control unit 31 may acquire the input history from the checklist DB 42. Specifically, the control unit 31 requests the server 20 to transmit the input history. The control unit 21 searches the checklist DB 42 using the user ID as a key, and transmits the extracted records, that is, a predetermined number of records from the checklist 43 with the most recent saved date and time, to the information processing device 30. The control unit 31 acquires the transmitted records.

[0098] The control unit 31 displays the input history page 56 based on the acquired input history (step S512). The control unit 31 accepts the selection of the history field 842 (step S513). The control unit 31 displays the bibliographic information page 52 of the checklist 43 corresponding to the history field 842 for which the selection was accepted on the touch panel 35 in the display mode, and waits for the user to select the previous page button 65, the delete button 71, or the edit button 72 (step S514).

[0099] The control unit 31 determines whether or not selection of the edit button 72 has been accepted (step S515). If it is determined that selection of the edit button 72 has been accepted (YES in step S515), the control unit 31 returns to step S505. If it is determined that selection of the edit button 72 has not been accepted (NO in step S515), the control unit 31 determines whether selection of the delete button 71 has been accepted (step S516).

[0100] If it is determined that the selection of the Delete button 71 has been accepted (YES in step S516), the control unit 31 notifies the server 20 of the deletion of the checklist 43 corresponding to the history field 842 for which the selection was accepted in step S513 (step S517). The control unit 21 deletes the record related to the notified checklist 43 from the checklist DB 42. The control unit 21 may assign a flag indicating deletion to the record related to the notified checklist 43.

[0101] If it is determined that the selection of the delete button 71 has not been accepted (NO in step S516), that is, if it is determined that the selection of the previous page button 65 has been accepted, or after step S517 ends, the control unit 31 returns to step S512.

[0102] 19 and 20 are explanatory diagrams illustrating examples of how data recorded in the checklist DB 42 is utilized. FIG. 19 is a graph showing the number of findings regarding overhead line construction work. The horizontal axis of the graph represents items to be checked included in the checklist 43, grouped according to the purpose of data utilization. More specifically, the horizontal axis of the graph in FIG. 19 represents the type of findings that the auditor identified as "defective" regarding each electrical equipment construction work. The vertical axis of the graph represents the number of items judged as "defective" by the auditor. A summary of the contents of the graph is displayed below the graph.

[0103] The graph in FIG. 19 shows statistics relating to matters that an analyst has determined to be important after performing various analyses on the data recorded in the checklist DB 42, for example.

[0104] We will now explain the outline of how to create the graph in Figure 19. Table 1 shows an excerpt from Checklist 43 corresponding to "construction work." Note that although not included in Table 1, each confirmation item is associated with relevant laws and regulations and page numbers in the company manual.

[0105] [Table 1]

[0106] In the graph in Figure 19, the bar for "Common to all vehicles" indicates that the number of "poor" judgments for the common check items related to "vehicles," i.e., check items 4-1 to 4-6, 4-8, 4-9, 5-1, 5-2, 5-7, and 5-8 in Table 1, is "2." The bar for "Heavy Equipment" indicates that the number of "poor" judgments for the check items related to "Heavy Equipment," i.e., check items 4-1, 4-2, 4-4 to 4-6, and 4-8 in Table 1, is "0." The bar for "Aerial Work Platforms" indicates that the number of "poor" judgments for the check items related to "Aerial Work Platforms," ​​i.e., check items 4-1, 4-2, and 4-4 to 4-6 in Table 1, is "0."

[0107] It is advisable that the analyst should not simply count the number of "defective" items in Checklist 43, but should also consider the details of the electrical equipment work linked to the "Work Name" and the contents of the "Good Practices of Points of Indication and Guidance," "Improvement Details," and "Special Notes" columns in Checklist 43 to determine whether or not to count the number of judgments. For example, even if the auditor enters the confirmation item in 4-1 as "defective," if a lifting platform was not used for the work on that day, the analyst should not include that "defective" in the data for the "lifting platform" bar in Figure 19.

[0108] For example, when creating graphs in the same format on a regular basis for quarterly reports, the analyst may record the type of issue pointed out in association with each confirmation item in the checklist 43 shown in Table 1. The analyst can quickly create a graph such as the one shown in Figure 19 using a spreadsheet program or the like.

[0109] The graph in FIG. 19 may be generated by inputting a query requesting a report of findings that have repeatedly occurred in multiple electrical equipment construction projects into a large language model (LLM) such as GPT-4 or Gemini. The query requesting a report of findings that have repeatedly occurred in multiple electrical equipment construction projects includes, for example, a checklist DB 42 and a prompt such as, "Please summarize the cumulative number of findings related to overhead lines in ** year in a bar graph with the findings on the horizontal axis and the number of findings on the vertical axis." The query may include a checklist 43 extracted from the checklist DB 42 based on specific conditions and the prompt.

[0110] The large-scale language model is an example of a language model that uses a query and checklist data. The graph output from the large-scale language model to which the query is input is an example of statistics regarding the relationship between the types of findings and the number of check items for each type of findings that received a failure selection.

[0111] FIG. 20 shows an example of a summary page of a safety patrol result report for fiscal year 2023. The table shown in FIG. 20 is also created by, for example, an analyst performing various analyses on the data recorded in the checklist DB 42 and summarizing the items that the analyst determines to be important. The table in FIG. 20 may be generated by inputting a query including the checklist DB 42 and a prompt into a large-scale language model such as GPT-4 or Gemini.

[0112] A prompt might be, for example, "We will summarize the results of this year's safety patrols. Please refer to the database and summarize the repeated findings for each task, and output them in a table format. Please keep the task details to 10 characters or less, and the summary of corrections and special notes to 30 characters or less." Or, "Please output the task details and the findings in a list format." Prompts should be created appropriately depending on the characteristics of the large-scale language model being used. The table shown in Figure 20 is an example of an answer output from a large-scale language model, including multiple repeated findings.

[0113] The user may visually check each record in the checklist DB 42, correct any input errors or clerical errors made by the auditor, and correct any incomplete natural language text entered in the "Points to be corrected, Good examples" column, etc., before inputting the result into the large-scale language model. By inputting an appropriately corrected checklist 43, it can be expected that the answers output from the large-scale language model will be more appropriate.

[0114] According to this embodiment, the checklist 43 entered during a construction site patrol can be easily confirmed by the user who entered it by selecting the edit button 62. Furthermore, the user can edit the checklist 43 by selecting the edit button 72. Therefore, it is possible to provide an information processing system 10 that allows the user to enrich the entries in the checklist 43 by utilizing the time spent traveling by public transportation, for example.

[0115] At a construction site, the user only needs to perform simple tasks such as selecting one of three options - "good," "bad," or "not applicable" - for each confirmation item on the checklist 43, and can complete an audit patrol in almost the same amount of time as using a paper checklist, for example.

[0116] When providing feedback after checking the site, the user can emphasize dialogue with the site representative, etc., and make simple notes on the checklist 43, and can supplement the entries after the feedback is complete. By supplementing the entries while traveling, the user can improve the efficiency of the audit work.

[0117] Because the checklists 43 are recorded as needed in the checklist DB 42, a user other than the user in charge of the audit can quickly perform a cross-sectional analysis of the checklists 43 of multiple construction sites. Because the checklists 43 are digitized from the input stage, it is possible to provide an information processing system 10 that contributes to the rapid introduction of data analysis and report creation using generative AI such as large-scale language models.

[0118] [Embodiment 2] 21 is an explanatory diagram illustrating the configuration of an information processing system 10 according to the second embodiment. This embodiment relates to a form in which the information processing system 10 is realized by combining and operating a general-purpose server computer 90 and a program 97. Explanations of parts common to the first embodiment will be omitted.

[0119] The server computer 90 includes a reading unit 29 in addition to the control unit 21, main memory device 22, auxiliary memory device 23, communication unit 24, and bus described above.

[0120] The program 97 is recorded on a portable recording medium 96. The control unit 21 reads the program 97 via the reading unit 29 and stores it in the auxiliary storage device 23. The control unit 21 may also read the program 97 stored in a semiconductor memory 98, such as a flash memory, implemented in the server computer 90. Furthermore, the control unit 21 may download the program 97 from a server computer (not shown) connected via the communication unit 24 and a network (not shown), and store it in the auxiliary storage device 23.

[0121] The program 97 is installed as a control program for the server computer 90, and is loaded into the main storage device 22 and executed. The control unit 21 transmits the portion of the program 97 to be executed by the control unit 31 to each information processing device 30 via the network. The transmitted program is installed as a control program for the information processing device 30, and is loaded into the control unit 31 and executed. In this way, the information processing system 10 described in the first embodiment is realized.

[0122] The program is an example of a program product. A computer program can be deployed to be executed on a single computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.

[0123] The technical features (constituent elements) described in each embodiment can be combined with each other, and by combining them, new technical features can be formed. The embodiments disclosed herein are illustrative in all respects and should not be considered as limiting. The scope of the present invention is defined by the claims, not by the above meaning, and is intended to include all modifications within the meaning and scope of the claims.

[0124] Independent and dependent claims may be combined with each other in any combination, regardless of the reference format. Furthermore, while the claims may be written in a format in which a claim references two or more other claims (multiple claim format), this is not a limitation. Multiple claims that reference at least one other claim (multiple multiple claim format) may also be written. [Explanation of symbols]

[0125] 10 Information Processing Systems 20 servers 21 Control section 22 Main storage 23 Auxiliary storage device 24 Communications Department 29 Reading unit 30 Information processing equipment (computer) 31 Control Unit 32 Main storage 33 Auxiliary storage device 34 Communications Department 35 Touch Panel 351 Input section 352 Display section 37 Camera 38 GPS 41 User DB 42 Checklist DB 43 Checklist 51 Top Page 52 Bibliographical information page 53 Checklist Page 535 Final Checklist Page 55 Shared team list screen 56 Input History Page 57 Checklist page 61 New input button 62 Edit button 63 Cancel button 64 Next page button 65 Previous page button 66 Save and exit button 67 Top button 68 New button 71 Delete button 72 Edit button 73 Reload Button 74 Sort button 75 Add Member Button 811 Title column 812 Implementation date column 813 Weather column 814 Implementer column 815 Construction Project Name 816 Work content column 821 Check box 831 Comments column 832 Improvement details column 833 Special Notes 834 Attachment field 841 Search field 842 History column 843 Title Block 844 Date column 845 Weather column 90 Server Computers 96 Portable recording media 97 Programs 98 Semiconductor Memory

Claims

1. Output multiple check items for each of the multiple check items related to electrical equipment construction, Accept the user's response to each confirmation item that is output, storing checklist data that associates the received response, the first identification information assigned to the user, and the second identification information related to the electrical equipment construction work; displaying a list of checklist data stored in association with the first identification information assigned to the user who is currently operating the device and the second identification information from among the plurality of stored checklist data; Accept the selection of checklist data to be edited, Outputting each confirmation item included in the selected checklist data and a response to the confirmation item. An information processing method in which processing is performed by a computer.

2. receiving modification instructions regarding the response; Edit the output checklist data based on the received change instructions. The information processing method according to claim 1 .

3. Accept input of findings regarding the electrical equipment construction work, the checklist data includes the response, the first identification information, the second identification information, and the received indications; A query requesting a report of recurring findings in multiple electrical equipment construction projects, and a language model using the checklist data, outputting an answer including the recurring findings.

3. The information processing method according to claim 1.

4. The response acceptance accepts a selection from good, bad and not applicable. The information processing method according to claim 1 .

5. The confirmation items are associated with the types of the identified items, A query for obtaining statistics regarding the relationship between the type of identified item and the number of check items for which a defect has been selected for each type of identified item, and a language model using the checklist data, are used to output statistics regarding the relationship between the type of identified item and the number of check items for which a defect has been selected for each type of identified item. The information processing method according to claim 4.

6. A list of the second identification information including the date and time and the construction project name of the electrical equipment construction is output in a selectable manner. The information processing method according to claim 1 .

7. Output information on whether each of the above confirmation items corresponds to a key item. The information processing method according to claim 1 .

8. Accept input of improvements or special notes, The checklist data includes the received improvement contents or special notes. The information processing method according to claim 1 .

9. Accepts the specification of attachments, The checklist data includes information about received attachments. The information processing method according to claim 1 .

10. The confirmation items are divided into multiple pages, When outputting the confirmation items for the last page, a save / end button is also output to save the checklist data and end the acceptance of responses. The information processing method according to claim 1 .

11. For each team consisting of multiple users, share checklist data related to each user's work. The information processing method according to claim 1 .

12. Accepting registrations to add users to said team; The plurality of confirmation items for each confirmation item are determined for each team. The information processing method according to claim 11.

13. Output multiple check items for each of the multiple check items related to electrical equipment construction, Accept the user's response to each confirmation item that is output, storing checklist data that associates the received response, the first identification information assigned to the user, and the second identification information related to the electrical equipment construction work; displaying a list of checklist data stored in association with the first identification information assigned to the user who is currently operating the device from among the plurality of stored checklist data; Accept the selection of checklist data to be edited, Outputting each confirmation item included in the selected checklist data and a response to the confirmation item. A program that causes a computer to perform a process.

14. An information processing device having a control unit, The control unit Output multiple check items for each of the multiple check items related to electrical equipment construction, Accept the user's response to each confirmation item that is output, storing checklist data that associates the received response, the first identification information assigned to the user, and the second identification information related to the electrical equipment construction work; displaying a list of checklist data stored in association with the first identification information assigned to the user who is currently operating the device from among the plurality of stored checklist data; Accept the selection of checklist data to be edited, Outputting each confirmation item included in the selected checklist data and a response to the confirmation item. Information processing device.

Images