JP2024091203A - Processing device, processing program, and processing method - Google Patents

Abstract

The present invention provides a new processing device, processing program, and processing method for a task relating to screening to grant a specified qualification to a company.
[Solution] In a processing system in which a terminal device installed within a company undergoing listing review and a server device that manages tasks based on received instruction input are communicatively connected via a network, the server device is a processing device equipped with at least one processor for creating a schedule of multiple tasks related to items to be evaluated in the review of the company, and when the at least one processor receives deadline information for the scheduled review, it sets a start or end deadline for the work period for each of the multiple tasks from the deadline information, sets the work period for each task based on the set start or end deadline and the standard work period set for each of the multiple tasks, and executes processing to output the work period set for each of the multiple tasks.
[Selected Figure] Figure 7A

Description

Application for application of Article 30, Paragraph 2 of the Patent Act has been filed 1. Publication 1 (1) Date of website posting October 1, 2022, October 31, 2022, November 4, 2022, November 24, 2022, and December 12, 2022 (2) Website address [October 1, 2022] Address 1: https://document.uniforce-cloud.com/Uniforce-IPO_service_outline_material.pdf [October 31, 2022] Address 2: https://ipo.uniforce-cloud.com/ Address 3: https://prtimes. jp/main/html/rd/p/000000014.000090278.html Address 4: https://uniforce.co.jp/ [November 4, 2022] Address 5: https://ipo.prd.uniforce-cloud.com/dashboard [November 24, 2022] Address 6: https://prtimes.jp/main/html/rd/p/000000010.000090278.html [December 12, 2022] Address 7: https://prtimes. jp/main/html/rd/p/000000015.000090278. html

Application for application of Article 30, Paragraph 2 of the Patent Act filed (3) Discloser: Uniforce Co., Ltd. (4) Contents of disclosed invention A. Uniforce Co., Ltd. has published service introduction materials and sales materials relating to the processing program, etc. invented by Higashikawa Hisamitsu and Ogawa Takuya on the Uniforce Co., Ltd. website at address 1 above. B. Uniforce Co., Ltd. has published services relating to the processing program, etc. invented by Higashikawa Hisamitsu and Ogawa Takuya on the Uniforce Co., Ltd. service site at address 2 above. C. PR TIMES Co., Ltd. has published services relating to the processing program, etc. invented by Higashikawa Hisamitsu and Ogawa Takuya through the PR TIMES Co., Ltd. websites at addresses 3, 6 and 7 above. D. Uniforce Co., Ltd. has published a service related to the processing program, etc. invented by Toshimitsu Higashikawa and Takuya Ogawa on the Uniforce Co., Ltd. website at the above address 4. E. Uniforce Co., Ltd. has published a service related to the processing program, etc. invented by Toshimitsu Higashikawa and Takuya Ogawa on the Uniforce Co., Ltd. website at the above address 5.

The present disclosure relates to a processing device, a processing program, and a processing method for tasks related to screening to grant specified qualifications to companies.

In the field of equipment maintenance work, equipment preservation support systems capable of automatically managing required tasks and their deadlines have been known for some time. For example, Patent Document 1 describes an equipment maintenance support system that includes a reception system, a mobile system, a network system, and a base system, in which the base system has a task management table in which multiple tasks are defined, and the reception system has a means for automatically transitioning the state of the reception system, the mobile system, and the network system to the next task, the second task, when the reception system receives a notification from the mobile system or the network system that a condition for transitioning to the next task, the second task, for any first task among the multiple tasks based on the task management table has been satisfied.

In cases such as facility maintenance work, each task can be clearly separated, and the number and variety of tasks themselves do not generally become enormous. Furthermore, the documents required for each task are not often related to each other, and it is generally easy to create the documents required for each task. For this reason, deadline management is easily achievable in facility maintenance work.

JP 2021-114098 A

The present disclosure has been made against the above background, and provides a new processing device, processing program, and processing method for tasks related to screening to grant specified qualifications to companies.

According to one aspect of the present disclosure, there is provided a processing device having at least one processor for creating a schedule of a plurality of tasks related to items to be evaluated in an audit of a company, the at least one processor being configured to execute a process for receiving deadline information for a scheduled audit, setting a start deadline or end deadline for a work period for each of the plurality of tasks from the deadline information, setting a work period for each of the tasks based on the set start deadline or end deadline and the standard work period set for each of the plurality of tasks, and outputting the work period set for each of the plurality of tasks for each of the plurality of tasks."

According to one aspect of the present disclosure, there is provided a processing program for causing a computer having at least one processor to execute a process for creating a schedule of a plurality of tasks related to items to be evaluated in an audit of a company, the processing program causing the at least one processor to function as follows: when receiving deadline information for a scheduled audit, set a start or end deadline for a work period for each of the plurality of tasks from the deadline information, set a work period for each of the tasks based on the set start or end deadline and the standard work period set for each of the plurality of tasks, and output the work period set for each of the plurality of tasks for each of the plurality of tasks.

According to one aspect of the present disclosure, there is provided a processing method executed by at least one processor in a computer having the at least one processor to execute processing for creating a schedule of a plurality of tasks related to items to be evaluated in an audit of a company, the processing method including the steps of: when receiving deadline information for a scheduled audit, setting a start deadline or end deadline for a work period for each of the plurality of tasks from the deadline information; setting a work period for each of the tasks based on the set start deadline or end deadline and a standard work period set for each of the plurality of tasks; and outputting the work period set for each of the plurality of tasks for each of the plurality of tasks.

The present disclosure provides a new processing device, processing program, and processing method for tasks related to screening to grant specified qualifications to companies.

The above effects are merely illustrative for the convenience of explanation and are not limiting. In addition to or instead of the above effects, any effect described in this disclosure or any effect obvious to a person skilled in the art may be achieved.

FIG. 1 is a diagram illustrating an outline of a deadline management process in a processing system 1 according to an embodiment of the present disclosure. FIG. 2 is a conceptual diagram illustrating a schematic configuration of a processing system 1 according to an embodiment of the present disclosure. FIG. 3 is a block diagram illustrating an example of a configuration of the terminal device 100 according to an embodiment of the present disclosure. FIG. 4 is a block diagram illustrating an example of a configuration of the server device 200 according to an embodiment of the present disclosure. FIG. 5A is a diagram conceptually illustrating a maintenance task management table stored in the server device 200 according to an embodiment of the present disclosure. FIG. 5B is a diagram conceptually illustrating a person in charge management table stored in the server device 200 according to an embodiment of the present disclosure. FIG. 5C is a diagram conceptually illustrating an operational task management table stored in the server device 200 according to an embodiment of the present disclosure. FIG. 5D is a diagram conceptually illustrating an assignment task management table stored in the server device 200 according to an embodiment of the present disclosure. FIG. 6A is a diagram showing a processing sequence executed between the terminal device 100 and the server device 200 according to an embodiment of the present disclosure. FIG. 6B is a diagram showing a processing sequence executed between the terminal device 100 and the server device 200 according to an embodiment of the present disclosure. FIG. 7A is a diagram showing a process flow executed in the server device 200 according to an embodiment of the present disclosure. FIG. 7B is a diagram showing a process flow executed in the server device 200 according to an embodiment of the present disclosure. FIG. 7C is a diagram showing a process flow executed in the server device 200 according to an embodiment of the present disclosure. FIG. 8A is a diagram showing an example of a screen output to the terminal device 100 according to an embodiment of the present disclosure. FIG. 8B is a diagram showing an example of a screen output to the terminal device 100 according to an embodiment of the present disclosure. FIG. 8C is a diagram illustrating an example of a screen output to the terminal device 100 according to an embodiment of the present disclosure. FIG. 8D is a diagram showing an example of a screen output to the terminal device 100 according to an embodiment of the present disclosure. FIG. 8E is a diagram showing an example of a screen output to the terminal device 100 according to an embodiment of the present disclosure. FIG. 8F is a diagram showing an example of a screen output to the terminal device 100 according to an embodiment of the present disclosure. FIG. 9 is a diagram illustrating an outline of an example of a schedule creation process executed in the server device 200 according to an embodiment of the present disclosure.

The embodiments of the present disclosure will be described with reference to the accompanying drawings, in which the same reference numerals are used to designate the same components.
1. Overview of the processing system 1 according to the present disclosure
The processing system 1 according to the present disclosure is used, for example, to set a work period for tasks related to items to be evaluated in an examination for granting a certain qualification to a company, and to perform schedule management of each task. Such a processing system is particularly used for managing tasks related to an examination (so-called listing examination) conducted when a company is listed on a specific stock exchange in order to enable trading of securities issued by the company. Of course, examples of tasks are not limited to tasks related to listing examination. Examples of such tasks include tasks in various examinations such as examinations for various standards set by the ISO (International Organization for Standardization), examinations for various certifications administered by national ministries and agencies and local governments, examinations by public or private rating agencies and evaluation agencies, and examinations conducted when investing or lending business funds to a company. In the following, a case of managing tasks related to listing examination will be described as an example of these.

When the processing system 1 receives information from a company indicating the future date on which the company plans to go public (e.g., 2022) and the company's fiscal year end date (e.g., December 31), the processing system 1 sets multiple tasks that need to be processed in the listing review based on the information, and a start deadline (scheduled start date) or end deadline (scheduled end date) for each task. Then, based on the set start or end deadline and the standard work period set for each task, the processing system 1 sets a work period for each task. In setting the work periods, the processing system 1 also takes into account the processing order set for the multiple tasks, optimizing task deadline management.

Furthermore, the processing system 1 requests the company to confirm whether the completed task is actually being operated appropriately, and manages new tasks based on the results.

FIG. 1 is a diagram showing an outline of a deadline management process related to a processing system 1 according to an embodiment of the present disclosure. Specifically, the example shows a case where a user is requested by Company A, the company to which the user belongs, to manage tasks related to evaluation items in a listing review. According to FIG. 1, Company A plans to be listed in fiscal year 2022, and the closing date of the said Company A is December 31st.

The server device constituting the processing system 1 creates a schedule for each task related to each evaluation item in the listing review based on the obtained listing year and settlement date. The processing system 1 then provides Company A with a task management table in which the work periods for tasks are displayed in a dashboard based on the created schedule. In particular, the processing system 1 according to the present disclosure makes it easier for users to grasp task deadline management based on the dashboard information, making deadline management itself easy to perform.

In addition, in the processing system 1, when the preparation of a task for each evaluation item is completed, the actual operation status of the prepared task is grasped, and when the input of issues that have become clear through the operation is received from Company A, the task for that issue can also be managed. For example, if "preparation of employee invention regulations" is set as a task, operation is actually started in accordance with the regulations. Then, when a predetermined period of time has passed since the operation started, a confirmation of the operation status is prompted. For example, if "no explanatory meeting on employee invention regulations has been held for some employees" is accepted as an issue through this confirmation, a new task "holding an explanatory meeting on employee invention regulations for some employees" is registered as a new task. In this way, it is possible to not only simply manage the progress of tasks related to evaluation items in the listing review, but also to manage their operation status, and further manage newly discovered issues and the response status to them.

In this disclosure, "task" simply means work or tasks related to the evaluation items in the listing review. In particular, in this disclosure, "tasks" are subdivided based on specialized knowledge related to listing reviews, and a huge number of tasks, more than several dozen, have been set. However, the content and quantity of the "tasks" are not fixed, and the content and quantity can be set as appropriate.

In addition, in the embodiment of the present disclosure, a case where the "designated deadline" is automatically set based on the fiscal year and settlement date of the planned listing will be described as an example. However, the designated deadline is not limited to a date, and may be set in weeks or hours. Similarly, in the embodiment of the present disclosure, a date that is set in advance for each task on the server device side will be described as an example of the "offset value", but the "offset value" is not limited to a date, and may be set in weeks or hours. And in the embodiment of the present disclosure, a date calculated by subtracting the offset value from the designated deadline will be described as an example of the end deadline of each task, but the end deadline is not limited to a date, and may be set in weeks or hours. Similarly, the start deadline of each task in the present disclosure may be set in weeks or hours, and is not limited to a start date. That is, in the present disclosure, the schedule of the tasks related to the evaluation items in the listing review can be managed on a daily, weekly, or hourly basis.

In addition, in the embodiment of the present disclosure, the "designated deadline" and "task end deadline" are described as examples of internal company dates, but are not limited to dates related to the inside of a company, etc. In other words, in the present disclosure, the "designated deadline", "task end deadline", and "task start deadline" are not limited to deadlines such as dates related to inside or outside a company, and include dates related not only to general companies but also to certain organizations (e.g., professional services). In other words, the schedule management of tasks related to the listing review business of the present disclosure may also be performed within certain organizations such as offices and corporations other than a company.

Note that in this disclosure, the names given to each device are used merely to distinguish each device from others, and each device may be given a different name depending on its function.

Furthermore, even if the disclosure includes descriptions such as "first" and "second," this does not mean that the description is limited to only the two elements to which the description is attached. Naturally, the disclosure may include a "third," a "fourth," and more elements.
2. Configuration of Processing System 1
2 is a conceptual diagram illustrating a schematic configuration of a processing system 1 according to an embodiment of the present disclosure. As illustrated in FIG. 2, the processing system 1 includes a terminal device 100 installed in a company undergoing listing examination, and a server device 200 that manages tasks based on instruction inputs received by the terminal device 100. Here, the terminal device 100 and the server device 200 are connected to each other via a network 300 so as to be able to communicate bidirectionally. The network 300 is, for example, the Internet. That is, the terminal device 100 and the server device 200 are connected to an Internet line by wire or wirelessly, and are capable of transmitting and receiving various information and the like.

In the example of FIG. 2, only one terminal device 100 is shown, but multiple terminal devices 100 may be installed in the company undergoing listing review or available to employees of the company and connected to be able to communicate via the network 300.

In addition, although the server device 200 is described as a single device, it is also possible to distribute each component and process of the server device 200 to multiple server devices or cloud server devices.

Furthermore, although the server device 200 is described as an example of a processing device, the processing device may be something other than the server device 200. For example, the processing device may be a terminal device used by a person in charge of conducting listing examinations in a company, or a terminal device installed in an examination organization that conducts listing examinations, a securities company, an auditing firm, or an office of various professionals that supports a series of procedures related to listing, etc.
3. Configuration of the terminal device 100
Fig. 3 is a block diagram showing an example of a configuration of a terminal device 100 according to an embodiment of the present disclosure. The terminal device 100 does not need to include all of the components shown in Fig. 3, and may have a configuration in which some components are omitted, or may include other components.

The terminal device 100 is typically a terminal device capable of wireless communication, such as a laptop computer or a desktop computer, but is of course not limited to such devices. For example, the terminal device 100 can be suitably applied to any device capable of executing the program related to the present disclosure, such as a smartphone, feature phone, personal digital assistant, or PDA. Also, as described above, when multiple terminal devices 100 are capable of communicating with the server device 200, the terminal devices 100 do not necessarily have to be the same type or the same terminal device, and may be different types of terminal devices.

As shown in FIG. 3, the terminal device 100 includes an output interface 111, a processor 112, a memory 113 including RAM, ROM, or non-volatile memory (or HDD in some cases), a communication interface 114 including a communication processing circuit and an antenna, and an input interface 115 including a mouse 115a and a keyboard 115b. These components are electrically connected to each other via control lines and data lines.

The output interface 111 functions as an output unit that outputs display information received from the server device 200 to a device such as a display or a printer by executing a program according to the present disclosure in response to an instruction from the processor 112. Such a display may be, for example, a liquid crystal display, an organic electroluminescence display, or electronic paper.

The processor 112 is composed of a CPU (microcomputer) and functions as a control unit that controls other connected components based on various programs stored in the memory 113. Specifically, the processor 112 reads out and executes programs for executing various applications and programs for executing the OS from the memory 113. In this disclosure, the processor 112 particularly executes a part of the processing described in the processing sequence described below. Details of the processing will be explained in detail in the explanation of FIG. 6A and subsequent figures. The processor 112 may be composed of a single CPU, or may be composed of a combination of multiple CPUs and GPUs.

The memory 113 is composed of a ROM, a RAM, a non-volatile memory, a HDD, etc., and functions as a storage unit. The ROM stores instructions for executing the application and OS related to the present disclosure as a program. The RAM is used to write and read data while the program stored in the ROM is being processed by the processor 112. The non-volatile memory is a memory into which data is written and read by the execution of the program, and data written therein is saved even after the execution of the program has ended. In the present disclosure, the memory 113 particularly stores a program for executing a part of the processing described in the processing sequence described below. Details of the processing will be explained in detail when explaining FIG. 6A and subsequent figures.

The communication interface 114 functions as a communication unit that transmits and receives information to and from the server device 200 installed remotely via a communication processing circuit and an antenna. The communication processing circuit processes the programs and various information used in the processing system 1 to transmit and receive information from the server device 200 according to the progress of processing. The communication processing circuit processes based on a wideband wireless communication method such as the LTE method, but it is also possible to process based on a method related to narrowband wireless communication such as wireless LANs such as IEEE802.11 and Bluetooth (registered trademark) or a method related to contactless wireless communication. It is also possible to use wired communication instead of or in addition to wireless communication.

The input interface 115 is composed of, for example, a mouse 115a and a keyboard 115b, and functions as an input unit that accepts instruction inputs related to the execution of the program according to the present disclosure and operation inputs for registering various information. The mouse 115a and the keyboard 115b are connected wirelessly or by wire to a main body including the processor 112 and the like. Note that the configuration of the input interface 115 is not limited to this, and a touch panel or other hard keys may be used. For example, when a touch panel is used, the touch panel is arranged to cover the output interface 111, and information on position coordinates corresponding to the data of an image output from the output interface 111 to the display is transmitted to the processor 112. As the touch panel method, known methods such as a resistive film method, a capacitive coupling method, and an ultrasonic surface acoustic wave method can be used. In the present disclosure, the touch panel detects swipe operations and tap operations on each icon, etc. displayed on the output interface 111 by an indicator.

4. Configuration of the server device 200 Fig. 4 is a block diagram showing an example of the configuration of the server device 200 according to an embodiment of the present disclosure. The server device 200 does not need to include all of the components shown in Fig. 4, and may have a configuration in which some components are omitted, or other components may be added. In addition, the server device 200 does not need to include the components shown in Fig. 4 in a single housing, and each component and process of the server device 200 may be distributed to multiple server devices or cloud server devices.

As shown in FIG. 4, the server device 200 includes a memory 211 including a RAM, a ROM, a non-volatile memory, an HDD, etc., a processor 212 including a CPU, etc., an input/output interface 213, and a communication interface 214. These components are electrically connected to each other via control lines and data lines.

Memory 211 includes RAM, ROM, non-volatile memory, and HDD, and functions as a storage unit. ROM stores instructions for executing the application and OS related to the present disclosure as a program. Such a program is loaded and executed by processor 212. RAM is used to write and read data while the program stored in ROM is being processed by processor 212. Non-volatile memory is memory into which data is written and read by the execution of the program, and data written therein is retained even after execution of the program has ended.

In the present disclosure, the memory 211 stores programs for "setting a start or end deadline for a work period for each of a plurality of tasks from deadline information when receiving deadline information for a scheduled review," "setting a work period for each task based on the set start or end deadline and the standard work period set for each of a plurality of tasks," "outputting the work period set for each of a plurality of tasks," "automatically assigning a person in charge to each of a plurality of tasks," "storing status information indicating the status of each of a plurality of tasks," "determining whether a predetermined period has passed since the end of each of a plurality of tasks based on the status information," and "outputting a confirmation request to request confirmation of the current status of a task for which a predetermined period has passed if the predetermined period has passed," and the like. The memory 211 also stores information on users authorized to use the server device 200, information on each task, general information on listing review, and legal information on listing review operations.

The processor 212 is composed of a CPU (microcomputer) and functions as a control unit for controlling other connected components based on various programs stored in the memory 211. Specifically, the processor 212 reads out and executes a program for executing an application related to the present disclosure and a program for executing an OS from the memory 211. In the present disclosure, the processor 212 executes, in particular, "a process of setting a start deadline or end deadline for a work period for each of a plurality of tasks from the deadline information when receiving deadline information for a scheduled review", "a process of setting a work period for each task based on the set start deadline or end deadline and the standard work period set for each of a plurality of tasks", "a process of outputting the work period set for each of a plurality of tasks for each of a plurality of tasks", "a process of automatically assigning a person in charge to each of a plurality of tasks", "a process of storing status information indicating the status of each of a plurality of tasks", "a process of determining whether a predetermined period has passed since the end of each of a plurality of tasks based on the status information", and "a process of outputting a confirmation request for requesting confirmation of the current status of a task for which a predetermined period has passed when a predetermined period has passed". The processor 212 may be composed of a single CPU, or may be composed of multiple CPUs.

The input/output interface 213 functions as an output unit that outputs information received from the terminal device 100 and information related to the listing review to a device such as a display or printer by executing the program related to the present disclosure in response to an instruction from the processor 212. Such a display may be, for example, a liquid crystal display, an organic electroluminescence display, or electronic paper. The input/output interface 213 also functions as an input unit that accepts instruction inputs related to the execution of the program related to the present disclosure and operation inputs for registering various information. For example, a mouse and a keyboard are connected wirelessly or by wire. The configuration of the input/output interface 213 is not limited to this, and a touch panel or other hard keys may be used. As the touch panel method, known methods such as a resistive film method, a capacitive coupling method, and an ultrasonic surface acoustic wave method can be used.

The communication interface 214 functions as a communication unit that transmits and receives information to and from the terminal device 100 and other server devices installed remotely via a communication processing circuit and an antenna. The communication processing circuit processes the programs and various information used in the processing system 1 to transmit and receive information from the terminal device 100 and other server devices according to the progress of processing. The communication processing circuit processes based on a wideband wireless communication method such as the LTE method, but it is also possible to process based on a method related to narrowband wireless communication such as wireless LANs such as IEEE802.11 and Bluetooth (registered trademark) or a method related to contactless wireless communication. It is also possible to use wired communication instead of or in addition to wireless communication.

Note that the input/output interface 213 and the communication interface 214 may be configured as a common interface when devices of the same standard are used. For example, when the input/output interface 213 is a connection device that performs wireless communication, the input/output interface 213 may be included in the communication interface 214.

5. Information stored in the memory 211 of the server device 200 FIG. 5A is a diagram conceptually illustrating a maintenance task management table stored in the server device 200 according to an embodiment of the present disclosure. The information stored in the maintenance task management table includes a higher-level task, a middle-level task, a lower-level task, a related task ID, a department, a position, a standard work period, an offset value, a person in charge, a status, a start date, an end date, and work details, which are stored in association with a task ID. Of these, the offset value is information that is registered as an initial state from the start of use of the processing system 1, regardless of whether or not a schedule management request is sent from the terminal device 100. In addition, the person in charge, the status, the start date, and the end date are information that is automatically input when a schedule management request is made from the terminal device 100 to the server device 200, and are information that can be changed by additional information and update information received from the terminal device 100. In addition, the work details are information that can be input or changed by update information received from the terminal device 100 when schedule management is started and an actual task is progressing.

"Task ID" is an identification number given to each task related to the evaluation items in the listing examination. Although not particularly clearly shown in FIG. 5A, there are two types of task IDs. That is, the format of the ID given to the higher-level tasks described later is different from that given to the mid-level tasks and lower-level tasks described later. As an example, the higher-level tasks are given a code such as "xx" or "yy". On the other hand, the mid-level tasks and lower-level tasks are given a hyphen and a serial number after the code of the higher-level task (for example, "xx-001", "yy-001"). This associates the higher-level task with its constituent mid-level tasks and lower-level tasks, making it easier to identify the tasks. The format of the task ID is not limited to the above content, and any format may be used as long as it is possible to identify each task. For example, numbers, letters, or other symbols may be added to the "xx" and "yy" parts.

Tasks related to the evaluation items in the listing review are hierarchically divided into three stages: "higher-level tasks," "mid-level tasks," and "lower-level tasks." In other words, the contents of the evaluation items are divided into parent tasks (higher-level tasks), child tasks (mid-level tasks), and grandchild tasks (lower-level tasks). For this reason, there are multiple mid-level tasks within a higher-level task, and multiple lower-level tasks within each mid-level task. However, depending on the contents of a mid-level task, there may be no lower-level tasks. Note that the task hierarchy is not limited to three stages, and may be set to two or four or more, and may be changed as appropriate to suit the evaluation items in the industry to which the user belongs.

The maintenance task management table stores task names for each of the higher-level tasks, mid-level tasks, and lower-level tasks. For convenience, FIG. 5A lists "B1" and "B2" as higher-level task names, "C1" and "C2" as mid-level tasks, and "D1" and "D2" as lower-level tasks, but in reality, task names related to the contents of the listing review work are stored in advance.

"Top tasks" are tasks that are set as a broad concept, taking into consideration the content and progress of the evaluation items in the listing review. For example, "Establishment and implementation of rules for the division of duties," "Establishment and implementation of rules for managing outsourced work," "Establishment and implementation of rules for the board of directors," "Establishment and implementation of rules for inventions made during the course of business," and "Establishment and implementation of rules for information security" are set as top tasks. Note that these tasks are typical tasks that are generally known as evaluation items in the listing review, but the types of top tasks are not limited to the above five.

"Mid-level tasks" are tasks that are set as intermediate tasks that are necessary to execute higher-level tasks, taking into consideration the content of the evaluation items in the listing review and their relationship with the higher-level tasks. In particular, "mid-level tasks" are stipulated to include content related to preparation for executing higher-level tasks, preparation of necessary documents, audits, etc. For this reason, when all mid-level tasks are completed, the higher-level tasks that are located above the mid-level tasks will also be completed. Also, while there may be mid-level tasks with the same name set for each higher-level task, the content of the mid-level tasks themselves differs depending on the content of the higher-level tasks. In other words, even if the task names of mid-level tasks are the same, the lower-level tasks included in the mid-level tasks will be different.

For example, if the higher-level task is "Establishment and operation of information security regulations," then mid-level tasks would include "Creating a list of tasks for each department," "Creating templates," "Establishing a project team," "Creating draft regulations," and "Approval by the board of directors." Note that these tasks are also typical tasks that are generally known as evaluation items, but mid-level tasks are not limited to these.

"Lower-level tasks" are tasks that are set as detailed tasks required to execute a mid-level task, taking into consideration the content of the evaluation items in the listing review and their relationship with the mid-level task. In particular, "lower-level tasks" are tasks that indicate mid-level tasks in detail and specifically, and stipulate details of documents, responses to documents, various required materials, etc. For this reason, when all lower-level tasks are completed, the mid-level tasks that are located above the lower-level tasks will also be completed.

For example, if the higher-level task is "Establishment and operation of information security regulations" and the mid-level task is "Establishment of a project team," then lower-level tasks will be set such as "Creating project member recruitment requirements," "Assigning project members," "Briefing sessions for project members," and "Defining roles within the project team." Note that the above lower-level tasks are merely representative examples, and in reality, a huge number of lower-level tasks, more than dozens, will be set.

"Related task ID" is the task ID of a related task when there is a content-related relationship between lower level tasks. In other words, when there is a strong business relationship between the lower level tasks, there is common work or materials, or the work flows are similar, the "Related task ID" field stores the task ID of the other related task, and if there are no other related tasks, the field is left blank. Note that for higher level tasks and mid-level tasks, the content of the tasks is set to be broad, so related task IDs are not stored.

As shown in FIG. 5A, related task IDs may be stored when there is a common mid-level task. For example, the related task ID column for task IDs "xx-006" and "xx-007" stores the other party's ID to indicate that the tasks are related. This makes it possible to confirm the relationship between task ID "xx-006" and task ID "xx-007", providing information for deciding whether to assign the same person in charge to both tasks, for example.

Even if the higher-level task and the mid-level task do not have anything in common, the related task ID may be stored. For example, the ID of the other party is stored in the related task ID column for the IDs "xx-006" and "yy-002" to indicate that the tasks are related to each other. In other words, even if the work content is completely different or the documents to be created are completely different, the related task ID may be stored after a comprehensive judgment of the commonality of the work or documents. Even in such cases, it provides information for deciding whether to assign the same person to both tasks, and is extremely useful information especially in cases where the relationship is thought to be low just by checking the task names of the lower-level tasks.

"Department" is information about the department that actually performs each task. Since the tasks are related to the evaluation items in the listing review, the "department" stores the name of the department that is expected to carry out the review-related work, such as IR, accounting, legal affairs, or general affairs. However, depending on the documents or materials to be prepared, the technical department or manufacturing department may be in charge. Note that, since the actual department name may differ from the name stored in "department" depending on the user, or may not exist, the information stored as "department" can be changed as appropriate using user information, and may even be excluded from the initial settings. In addition, for higher-level tasks, the content of the task is set to be broad, and it is possible that multiple departments may handle the task, so the setting is such that "department" is not stored.

"Position" is information about the position required to actually perform each task. "Position" stores information that limits who can perform a task depending on the importance of the task, such as general position or above, chief or above, section manager or above, department manager or above, etc. Note that, depending on the user, the actual job title may differ from the name stored in "Position" or may not exist, so the information stored as "Position" can be changed as appropriate based on user information, and may even be excluded from the initial settings.

"Standard work period" is information about the industry standard work hours required to perform each task. For this reason, the "standard work period" column stores the time (number of days) generally required to complete a task, rather than information that takes into account the ability or experience of the person performing the task. Here, since a mid-level task is completed when all lower level tasks are completed, the standard work period for a mid-level task is greater than the total standard work time for the lower level tasks contained in that mid-level task. Note that the content of higher level tasks is set to be broad, so the "standard work period" is not stored.

The "offset value" is set to set and manage the schedule for the execution of each task. The "offset value" is set in advance for each task, taking into account, for example, the standard work period of mid-level tasks and lower-level tasks. The setting is performed appropriately by the administrator of the server device 200, and the user is not involved. By using such an "offset value," when responding to a change in the specified deadline (first deadline) or duplicating a schedule, the work period, start date, and end date can be easily set taking into account holidays (non-working days) such as Saturdays and Sundays, unlike when simply setting the work period.

"Person in Charge" is information about the name of the person who actually carries out each task. "Person in Charge" is information that is automatically set and stored when a schedule management request is made from the terminal device 100 to the server device 200. However, depending on the user's situation, there may be no relevant person when the request is made, in which case "not assigned" is stored. Furthermore, when the server device 200 receives additional information about the person in charge from the terminal device 100, the "Person in Charge" is newly set or updated. Note that for higher-level tasks, the content of the task is set broadly, and the "Person in Charge" is set not to be stored.

"Status" is progress information for each task. The "Status" column stores either "Not started," "In progress," or "Completed," as well as the actual completion date. When task schedule management begins, "Not started" is stored as the status of each task, but depending on progress reports received from the terminal device 100, the stored information will change to "In progress" or even "Completed." Note that for higher-level tasks, the content of the tasks is set to be broad, and the "status" is set not to be stored.

The "start date" is information on the start date of each task, and the "end date" is information on the end date of each task. The "start date" and "end date" are information that are automatically set and stored when the terminal device 100 requests the server device 200 to manage the schedule. Here, the "end date" that is automatically set is the planned end date, which is the deadline, and the "start date" that is automatically set is also the planned start date calculated from the planned end date and the work period. However, the dates of the "start date" and "end date" will be updated according to the progress report received from the terminal device 100. Here, since a mid-level task is completed by executing all lower-level tasks, the start date of the mid-level task is the earliest date of the lower-level tasks included in the mid-level task, and the end date of the mid-level task is the latest date of the lower-level tasks included in the mid-level task. Note that the content of the upper-level tasks is set broadly, and the "start date" and "end date" are not stored.

"Work details" is detailed information required for the work of carrying out each task.

FIG. 5B is a diagram conceptually illustrating a person in charge management table stored in the server device 200 according to an embodiment of the present disclosure. The person in charge management table includes information on employees of the user company. Specifically, information on "person in charge," "department," "position," and "work history" is stored. Here, "person in charge" is the same information as "person in charge" in the maintenance task management table of FIG. 5A, and is also information that links the maintenance task management table and the person in charge management table. "Department" is information on the department name to which the person in charge of the task belongs, and department names such as "accounting," "legal affairs," "general affairs," or "IR" are stored. In addition, "position" is information on the position of the person in charge of the task, and job titles such as "department manager," "section manager," "section chief," "supervisor," and "general" are stored. This information is updated when there is a personnel transfer or department change in the user company.

"Work history" is information about the task IDs of tasks that each person in charge has been in charge of up until now. In other words, "work history" stores task information experienced by each person in charge. When automatically or manually assigning a new person in charge of a task, "work history" can be used to determine the most suitable person in charge by taking past performance into consideration. Even if there is no past performance of the same task, by combining it with the information on the related task ID described above, it is possible to automatically or manually assign someone with experience in related tasks as the person in charge, which also widens the range of people to choose from. In other words, "work history" is very useful information when assigning tasks.

In addition, the memory 211 may store a management table that combines the two table data, rather than storing the above-mentioned maintenance task management table and person in charge management table separately. In this case, the processor 212 of the server device 200 may appropriately generate a table composed of necessary information from the one table.

In addition to the maintenance task management table and the person in charge management table described above, the memory 211 of the server device 200 stores the listing year and settlement date of each company. The listing year and settlement date are set by the user when the user starts using the system (i.e., the initial setup stage). For example, information related to the listing year and settlement date may be sent from the terminal device 100 to the server device 200 and automatically stored in the server device 200, or may be set in the server device 200 after the administrator of the server device 200 receives separate contact from the user.

Figure 5C is a diagram conceptually illustrating an operation task management table stored in a server device 200 according to an embodiment of the present disclosure. In the operation task management table, higher-level tasks, mid-level tasks, lower-level tasks, and change dates are stored in association with task IDs. When the status of all lower-level and mid-level tasks of each higher-level task stored in the maintenance task management table is updated to "completed," the operation task management table stores each of the higher-level tasks, mid-level tasks, and lower-level tasks and their associated task IDs. Therefore, the information on the higher-level tasks, mid-level tasks, and lower-level tasks stored in the operation task management table is the same as the information in the maintenance task management table shown in Figure 5A.

"Change date" is information that indicates the date on which the stored table was changed so that each task stored in the maintenance task management table was newly stored in the maintenance task management table. In other words, this date indicates the date on which each higher-level task, as well as all of its lower-level mid-level and lower-level tasks, were completed and their status was updated to "Completed."

FIG. 5D is a diagram conceptually illustrating an assignment task management table stored in the server device 200 according to an embodiment of the present disclosure. In the assignment task management table, a higher-level task, a mid-level task, a start date, an end date, a date of indication, a person in charge, a status, and work details are stored in association with a task ID. Of these, the mid-level task, the start date, the end date, a date of indication, a person in charge, and work details are input based on new task information received from the terminal device 100 to the server device 200 when the new task information is received.

When new operational issues are discovered and new tasks are generated for each higher-level task managed in the maintenance task management table, they are stored in the issue task management table. In other words, when new task information is received from the terminal device 100, the issue task management table generates a task ID that identifies the new task and stores various information.

A "task ID" is an identification number given to a newly created task in an operation type, and to each task whose status, schedule, etc. are managed in that operation type. The task ID has two formats, one given to a higher-level task and one given to a lower-level or mid-level task, similar to the task ID in the maintenance task management table shown in FIG. 5A (lower-level tasks are omitted in FIG. 6C). The task ID also has the same hierarchy as the task ID in the maintenance task management table shown in FIG. 5A.

"Start date" is information on the start date of work for each task, and "end date" is information on the end date of work for each task. "Start date" and "end date" are information included in new task information input by a user or the like in the terminal device 100. Note that, as with the maintenance task management table shown in FIG. 5A, the start date and end date may be set automatically based on information such as the work period.

"Date of issue" is information on the date on which an issue was pointed out in the operation type and new task information was generated as a new task. When new task information is generated by a user or the like on the terminal device 100, the date of generation is automatically input as this date. Note that in addition to the date on which the new task information was generated, other dates may also be stored, such as the date on which the new task information was sent or the date on which it was input by a user or the like.

"Source of suggestion" is information for identifying the person or organization that pointed out an issue in the operation type and generated new task information as a new task. This information is included in the new task information entered by the user in the terminal device 100. Such sources of suggestion may include, for example, not only the operations staff or managers of the company to which the person belongs, but also securities companies, auditing firms, various professional offices and their staff members who support the series of procedures in the listing review.

"Status" is progress information for each task. The "Status" column stores either "Not started," "In progress," "Under review," "Under revision," or Completed, as well as the actual completion date. When task schedule management begins, "Not started" is stored as the status of each task, but when the terminal device 100 receives operational input to change the status of each task, the stored information changes to "In progress" or even "Completed."

"Work details" is detailed information required for the work of carrying out each task.

6. Processing sequence executed by the processing system 1 Figures 6A and 6B are diagrams showing a processing sequence executed between the terminal device 100 and the server device 200 according to an embodiment of the present disclosure. Below, the flow of the processing and information provided to the user will be described with reference to each figure.

First, FIG. 6A is a diagram showing a processing sequence at the stage where the schedule of each task is set and the processing of each task is actually executed in the processing system 1 according to the present disclosure. As shown in FIG. 6A, the terminal device 100 executes a startup process for starting a request for task schedule management (S11). Specifically, the processor 112 of the terminal device 100 displays a login screen on a display connected via the output interface 111. Thereafter, the processor 112 of the terminal device 100 receives a login ID and password (hereinafter, login information) entered by a terminal operator (e.g., a company employee) and transmits the received login information to the server device 200 via the communication interface 114. That is, the processor 112 of the terminal device 100 makes a login request to the processing system 1 to the server device 200 (T11).

When the server device 200 receives login information via the communication interface 214, the processor 212 of the server device 200 executes authentication processing (S12). Specifically, the processor 212 of the server device 200 compares the received login information with the user information stored in the memory 211 to determine whether the two pieces of information match. The processor 212 of the server device 200 transmits the authentication result to the terminal device 100 via the communication interface 114 (T12).

When the terminal device 100 receives an authentication result approving the login request via the communication interface 114, a screen for inputting the specified deadline is displayed on the display of the terminal device 100. On the other hand, when an authentication result not approving the login request is received via the communication interface 114, a screen requesting the user to re-enter login information is displayed on the display of the terminal device 100. Here, it is of course assumed that the login request is approved.

After a screen requesting input of the listing year and settlement date is displayed on the terminal device 100, the terminal operator inputs the listing year and settlement date that have been determined in advance within the company as user setting information (S13), and the processor 112 of the terminal device 100 receives the listing year and settlement date. The processor 112 of the terminal device 100 then transmits the received listing year and settlement date as setting information to the server device 200 via the communication interface 114 (T13). This means that a request for schedule management of tasks related to evaluation items in the listing review is executed from the terminal device 100 to the server device 200.

When the server device 200 receives the setting information via the communication interface 214, the processor 212 of the server device 200 stores the setting information in the memory 211 (S14). The processor 212 of the server device 200 then reads the program stored in the memory 211, executes a schedule creation process using the setting information, and creates schedule information by setting a work period for each task by counting backwards from a date determined by the listing year and the settlement date (for example, if the listing year is 2022 and the settlement date is December 31, 2022). A specific schedule creation process will be described later with reference to Figures 7A and 7B. Here, the schedule information includes a schedule table of all tasks shown in Figure 8A, a list of tasks shown in Figure 8B, and detailed information of each task shown in Figure 8C, and the work period of the task is dashboard-ized information. The schedule information is displayed on the display of the terminal device 100, and will be described later.

Then, the processor 212 of the server device 200 transmits the created schedule information to the terminal device 100 via the communication interface 214 (T14). That is, a response to the request for schedule management of the tasks related to the listing review items is sent from the server device 200 to the terminal device 100.

The processor 112 of the terminal device 100 displays the schedule information received via the communication interface 114 on a display unit such as a display via the output interface 111 (S16). Specifically, as shown in FIG. 8A, a schedule table is displayed in which the work period is displayed as a horizontal bar graph on a calendar for each task (higher-level task, middle-level task, lower-level task). The schedule table also displays the task name, start date, end date, status, and person in charge. In addition, in FIG. 8A, the higher-level task "Establishment and operation of information security regulations" is selected, and each of the middle-level tasks of "Establishment of a project team" is also selected, and each of the lower-level tasks is also displayed. In other words, when the "higher-level task" and "middle-level task" displayed in the task name column are clicked with the mouse 115a, each task located below the clicked task is displayed.

In the schedule information received in S16, the start date and end date columns show the planned start date and planned end date that were automatically set in S15. In addition, in the person in charge column, the name of the person in charge is displayed for the part that was automatically set in S15, and for the part that was not automatically set, "no applicable person" is displayed. On the other hand, the status column is not automatically determined in S15, and the initial status of "not started" is uniformly displayed.

As mentioned above, for higher-level and mid-level tasks, the higher-level tasks are completed when all tasks in the lower layers are completed, so the bar graphs showing the work periods for higher-level and mid-level tasks are displayed with the bar graphs showing the work periods for the tasks in the lower layers connected together. This makes it easy to grasp the detailed work periods for each lower-level task, while also making it easy to grasp the work periods for comprehensive tasks that are higher-level and mid-level tasks positioned in the upper layers. In other words, it becomes possible to simultaneously and easily grasp not only the individual tasks that each person in charge should be aware of, but also the overall task schedule that managers and others should be aware of.

Information displayed on the display of the terminal device 100 includes a task list as shown in FIG. 8B. For example, the display of FIG. 8A may be switched to the display of FIG. 8B by switching tabs, and the task list may be displayed alongside the schedule of FIG. 8A. As shown in FIG. 8B, the task list display can display all tasks, and it is also possible to display only some of the tasks by setting conditions. Specifically, the display allows selection of the task type, person in charge, status, start date, end date, and update period. Also, a keyword search for tasks is possible by inputting a keyword.

Below the display for selecting search conditions, a list of tasks is displayed as the search results. Display items for a task include, for example, the task name, type, status, and person in charge, but are not limited to these, and the display items for a task can be appropriately selected and changed by the terminal operator of the terminal device 100. For example, the terminal operator of the terminal device 100 can extract tasks that have not been assigned a person in charge or tasks that have not progressed (tasks that have not been started), making it easy to assign new people in charge and review schedules, etc.

Furthermore, the information displayed on the display of the terminal device 100 includes task details as shown in FIG. 8C. For example, by selecting the name of each task in FIG. 8B, the task details screen in FIG. 8C may be displayed. Also, by switching tabs, the display of FIG. 8A or FIG. 8B may be switched to the display of FIG. 8C, and the task details may be displayed in addition to the displays of FIG. 8A and FIG. 8B. As shown in FIG. 8C, the display of task details includes the name of the selected task (creating a business flow diagram), and above the name of the task, a display of the hierarchy related to the task (return to list > maintenance and operation of business flow > creating a business flow diagram) is included. This makes it easy to check the current task, and further makes it easy to transition from the selected task to other tasks and task lists.

Below the name of the selected task, the status, person in charge, start date, end date, work details, maintenance tasks, and related tasks are displayed. The status, person in charge, start date, and end date are linked to the entries in the schedule table in Figure 8A, and each content can be changed as appropriate. The work details and work tasks columns are fields that are entered by the terminal operator of the terminal device 100 as the actual task progresses.

The task details information includes related task information, and the name, work period, person in charge, and status of the task related to the selected task are displayed. That is, information related to the related task ID shown in FIG. 5A (i.e., the content of the related task) is displayed as detailed information on the selected task. This makes it easy to grasp not only the status of the selected task, but also the status of related tasks, and the terminal operator of the terminal device 100 can easily assign a new person in charge to a task that has not been assigned a person in charge or a task that has not progressed (a task that has not been started) and review the schedule, etc. In particular, it becomes possible to grasp the cross-sectional progress status of tasks, and schedule management of upper-level tasks and mid-level tasks can be achieved with high accuracy and ease.

The display also shows "Maintenance," which indicates the type of the selected task. Tasks lower in level than the creation of the business flow diagram are also displayed by type as maintenance tasks. This makes it easy to see what types of tasks have arisen as lower level tasks.

When the terminal operator checks the schedule information displayed on the display of the terminal device 100 and determines that there is content to be added or modified (additional setting information), the terminal operator inputs the additional setting information (S17), and the processor 112 of the terminal device 100 receives the additional setting information. The additional setting information includes, for example, an unspecified person in charge and an automatically set start date and end date for a task. The processor 112 of the terminal device 100 then transmits the received additional setting information to the server device 200 via the communication interface 114 (T15). As a result, a request to change the settings for schedule management of tasks related to evaluation items in the listing review is executed from the terminal device 100 to the server device 200.

When the server device 200 receives the additional setting information via the communication interface 214, the processor 212 of the server device 200 stores the additional setting information in the memory 211 (S18). As a result, the request for changing the settings of the schedule management of the task related to the listing review item is approved, and the user starts schedule management. If there is no additional setting information, the schedule management of the task starts from the stage of S16. If the start date and end date of the task are modified, the processor 212 of the server device 200 may perform the schedule creation process again. That is, the processor 212 of the server device 200 may take into account the modified start date or end date of the task, determine the need to modify the work period for other tasks, and reset the work period for one or more tasks. In this case, the processor 212 of the server device 200 may compare the start date and end date before the modification with the modified start date and end date to modify the offset value.

After that, as the task processing progresses, update information for the task is input by the terminal operator (S19), and the processor 112 of the terminal device 100 receives the update information. The update information includes, for example, information such as the date the task processing actually started and ended, and the newly assigned person in charge. The processor 112 of the terminal device 100 then transmits the received update information to the server device 200 via the communication interface 114 (T16). As a result, a request to update the schedule management of the task related to the listing review item is executed from the terminal device 100 to the server device 200.

When the server device 200 receives update information via the communication interface 214, the processor 212 of the server device 200 stores the update information in the memory 211 (S20). This approves the request to update the schedule management of the tasks related to the evaluation items in the listing review, and the schedule management is updated to the latest state. When the status of all the lower mid-level and lower-level tasks is updated to "Completed", the processor 212 of the server device 200 changes and stores the information of the upper task and the lower mid-level and lower-level tasks from the maintenance task management table to the operation task management table. Then, until new task information is received, each task is managed in the maintenance task management table.

Next, FIG. 6B is a diagram showing a processing sequence of the stage of confirming the current operational status of each task managed in the operational task management table in the processing system 1 according to the present disclosure. As shown in FIG. 6B, the processor 212 of the server device 200 refers to the operational task management table and reads out information on each task ID and its associated change date. The processor 212 then determines from among the read task IDs whether there is a task for which a predetermined period has passed since the change date. The processor 212 extracts the task for which it is determined that the predetermined period has passed (S31), and transmits a confirmation request (T31) to the terminal device 100 via the communication interface 214 to confirm the current operational status of the task (higher-level task).

When the processor 112 of the terminal device 100 receives the confirmation request, it displays the received confirmation request on a display unit such as a display via the output interface 111 (S31). Specifically, when the confirmation request is received, a notification indicating that a push notification has been received is displayed on the display unit of the terminal device 100. When the user clicks on the notification via the input interface 115, a confirmation request notification screen as shown in FIG. 8D is displayed. The confirmation request notification screen displays the notification content and the date and time of receipt. For example, when the upper task is "Maintenance and operation of business flow", assume that the change date is stored as October 1, 2022 because all the middle and lower tasks have been completed. When two months are preset as the predetermined period, the processor 212 of the server device 200 generates a confirmation request on December 1, 2022 with the content "Please check whether the business flow is being operated correctly" and transmits it to the terminal device 100. Therefore, the notification content "Please check whether the business flow is being operated correctly" is displayed on the display of the terminal device 100.

Next, the processor 112 of the terminal device 100 accepts input of the confirmation result by the user via the input interface 115 (S32). Specifically, the confirmation result registration screen shown in FIG. 8E is displayed on a display unit such as a display of the terminal device 100, and operation input by the user is accepted on this display screen. On the confirmation result registration screen, first, an input of whether or not the notification contents have been confirmed is made. Here, it is shown that the user's operation input selected "Yes", indicating that the confirmation has been made. Although not described in detail, if "No" is selected, the send buttons for the various information accepted on the confirmation result registration screen are disabled, and the information cannot be sent.

In addition, if the confirmation of the notification contents is selected, an operation input is accepted to confirm whether a problem is found based on the operation status of the task and whether a new task is registered to correct the problem. If "No" is selected here, confirmation result information can be sent to the server device 200 without activating the input box for new task registration thereafter. On the other hand, if "Yes" is selected, the registration box for the new task is activated and operation input by the user is accepted. Specifically, the input of the name of the lower task (middle task) linked to the task (higher task) for which the confirmation request was sent is accepted in the input box for the new task. In addition, the selection of the corresponding dates is accepted in the input boxes for the start date and end date of the new task. In the maintenance task management table, the start date and end date are automatically calculated from each piece of information such as the listing year, settlement date, and standard work period, but here, they can be determined by selecting the dates by the user. The input box for "source of issue" accepts input of information identifying the user who pointed out the issue (i.e., the investment manager or administrator of the company, securities firms, auditing firms, professional offices and their staff who support the series of procedures in the listing review, etc.). The information may be information about the user who made the input, or the user who pointed out the issue may be different from the user who actually made the input. The input box for "person in charge" accepts input of information identifying the person in charge of carrying out the task. This information is not required and may be automatically assigned by the server device 200. The input box for "work details" accepts input of detailed information required for the work of carrying out the task.

As an example of such new task information, suppose that as a result of receiving a confirmation request for a higher-level task called "Establishing and operating the business flow," a new task called "Holding a business flow briefing in the XX department" is generated. In this case, the processor 112 displays on the display unit the input of various items required for new task registration. The processor 112 then accepts input of "Holding a business flow briefing in the XX department" in the input box for the new task, the desired dates in the input boxes for the start date and end date, and the necessary information in the input boxes for the source of the suggestion, the person in charge, and the work details.

Returning to FIG. 6B, the processor 112 transmits the received information to the server device 200 as new task information (T32) via the communication interface 114. If it is selected that no new task is to be registered on the confirmation result registration screen, confirmation result information is transmitted indicating that the notification contents have been confirmed and that no new task is to be registered. The server device 200 then stores the date on which the information was received and the received confirmation result information in a maintenance task management table (not shown).

Meanwhile, when the processor 212 of the server device 200 receives new task information via the communication interface 214, it generates new task ID information and stores it in the assignment task management table (S33). The processor 212 then stores the date on which the new task was created as the date of indication, in association with the stored new task. When the processor 212 stores the received new task information and the date of indication in association with the task ID in the assignment task management table, it transmits operation management information (T33) indicating this to the terminal device 100 via the communication interface 214. Although not shown in the figure, the processor 112 of the terminal device 100 that has received the information notifies the user of the reception via the display unit.

Here, FIG. 8F is a diagram showing an example of an issue management screen displayed on a display unit such as a display of the terminal device 100. According to FIG. 8F, the issue management screen includes selection boxes below the screen name "Issue Management" for narrowing down the tasks currently managed in the issue task management table based on at least one of the person in charge, source of the issue, date of issue, start date, and end date. By selecting a filtering condition from each selection box, it is possible to further narrow down the tasks displayed in the status area displayed below.

Below each selection box, higher-level tasks such as "Development and operation of business flow", "Development and operation of information security regulations", and "Development and operation of employee invention regulations" are displayed in a selectable manner. In FIG. 8F, the higher-level task "Development and operation of business flow" is selected, and below the display, status areas are displayed corresponding to each status of "Not started", "In progress", "Review", "Modification", and "End". Then, from among the mid-level tasks registered under the higher-level task of "Development and operation of business flow", the tasks narrowed down by the selection box are displayed in the status area corresponding to the current status. In the status area, each task is shown in a tile-shaped box frame, and although not shown in particular, at least a part of the various information stored in the assignment task management table for each task is displayed in the box frame. Then, for example, when the person in charge completes the task that was being handled and the manager is reviewing it, the user can update the status by dragging and dropping the tile displayed in the "In progress" status area to the "Review" status area. Similarly, the status of the tiles displayed in each status area can be easily updated by dragging and dropping. Note that drag-and-drop is merely one example of how to move each tile, and other methods are of course possible, such as selecting the tile to be moved and the destination, and then moving it. Also, when a corner tile is selected, the screen transitions to a detailed display screen (not shown) for each task, and on this screen it is possible to display more information than that managed in the assignment task management table.

Returning to FIG. 6B, the processing sequence for updating the status will be described as explained in FIG. 8F above. As task processing progresses for each task stored in the assignment task management table, task update information is input by the terminal operator (S38). As an example, the update information includes the selection of the task to be updated by dragging and dropping a tile and updated status information, as shown in FIG. 8F. The processor 112 of the terminal device 100 then transmits the received update information to the server device 200 via the communication interface 114 (T35). As a result, a request to update the status of the task registered in the assignment task management table is executed from the terminal device 100 to the server device 200.

When the server device 200 receives the update information via the communication interface 214, the processor 212 of the server device 200 stores the update information in the memory 211 (S39). Specifically, the status of the assignment task management table is updated, and the information stored in the table is updated to the latest state. When the status of all mid-level tasks below the upper level task is updated to "Completed", the processor 212 of the server device 200 changes and stores the information of the upper level task and the mid-level task from the assignment task management table to the operational task management table. This ends the processing related to the processing sequence.

In this way, it is possible not only to process tasks related to the evaluation items in the listing examination, but also to appropriately manage the operation status after the tasks are processed and operation begins. Furthermore, when the operation status is confirmed and an issue is found, a new task to solve the issue is generated, and the schedule of the task can be managed in the same way. Therefore, the entire cycle from task processing, operation, and issue discovery can be efficiently managed.
7. Processing flow executed in the server device 200
Hereinafter, the schedule creation process (S15) shown in FIG. 6A will be described in detail with respect to a process flow executed by the server device 200.

FIG. 7A is a diagram showing a process flow executed in the server device 200 according to an embodiment of the present disclosure. The process flow is mainly performed by the processor 212 of the server device 200 reading and executing a program stored in the memory 211. FIG. 9 is a diagram showing a schematic overview of an example of a schedule creation process executed in the server device 200 according to an embodiment of the present disclosure.

As shown in FIG. 7A, the processor 212 determines whether or not setting information including the listing year and settlement date has been received from the terminal device 100 via the communication interface 214 (S101). If the setting information has not been received (S101: No), this processing flow ends. On the other hand, if the setting information has been received (S101: Yes), the processor 212 sets the date identified from the listing year and settlement date included in the setting information as the specified deadline and stores it in the memory 211 (S102). The following description assumes that December 31, 2022 has been set as the specified deadline (due date), as shown in FIG. 9.

Next, the processor 212 subtracts an offset value set in advance for each task from the stored designated deadline, and calculates and sets the end date, which is the in-house end date of each task, for each task (S103). Specifically, the processor 212 subtracts the offset value of each task stored in the memory 211 from the received designated deadline, and sets the end date of each task before the designated deadline, so that all tasks are completed by the designated deadline. For example, as shown in FIG. 9, for the task "Assign Roles in the Project Team", the processor 212 subtracts the set offset value of 106 days from the designated deadline (due date) of December 31, and sets the end date, which is the end date of the task, to September 16. Here, the task "Assign Roles in the Project Team" is a task that cannot be executed until the task "Assign Project Members" is completed, but since the number of days considering the order of task completion is set as the offset value, an appropriate end date can be set simply by subtracting the offset value from the designated deadline. Here, because the offset value is set to include only actual working days (Monday to Friday), the end date is set even earlier. For example, September 17th (Saturday) and September 18th (Sunday) are holidays and are therefore excluded from the offset, so the end date of a certain task becomes September 16th, 106 days before the specified deadline of December 31st. Note that in order to include only the actual working days, general calendar information is stored in memory 211, and processor 212 uses this calendar information to set the work period.

Next, the processor 212 sets the planned work period (work period at the time of initial setting) of each task from the end date of each task set in S103 and the standard work period of each task stored in the memory 211, and stores it in the memory 211 (S104). Specifically, the processor 212 sets the work period to September 16th, 1 day, for the task "Setting roles in the project team", based on the set end date of September 16th and the standard work period of 1 day stored in the memory 211. Here, the setting of the work period is set to target only actual working days, as in the case of the handling of offset values, so that if a holiday is included in the work period, the work period is set longer than the standard work period. Then, in the embodiment of the present disclosure, the end date calculated in the above process and the start date, which is the first day of the work period, are stored in the start date and end date columns of each task in FIG. 5A.

Next, the processor 212 generates dashboard information of the work period of each set task, and stores it in the memory 211 (S105). That is, in the stage of S34, the processor 212 sets only the numerical data of the work period of each chest, and generates information related to the graphical representation of the schedule as shown in FIG. 8A using the numerical data. The processor 212 also executes a process related to the automatic assignment of the person in charge of each task, and stores it in the memory 211 as schedule information (S106). For example, the processor 212 performs the automatic assignment based on the related task ID, department, position, and assignment history information stored in the memory 211. The automatic assignment will be described later with reference to FIG. 7B.

Then, the processor 212 transmits the schedule information with the person in charge automatically assigned to the terminal device 100 via the communication interface 214 (S107).

Next, a detailed process flow of S106 will be described with reference to FIG. 7B. FIG. 7B is a diagram showing a process flow executed in the server device 200 according to an embodiment of the present disclosure. This process flow is mainly performed by the processor 212 of the server device 200 reading and executing a program stored in the memory 211.

First, the processor 212 selects one task to which a person in charge is to be assigned from the tasks stored in the memory 211 (S301). The tasks to be selected are mid-level tasks and lower-level tasks, so for example, the processor 212 selects tasks excluding higher-level tasks in the order of task ID.

Next, the processor 212 calculates the number of people available to handle the selected task, taking into account the department and position (S302). Specifically, the processor 212 counts the target persons based on the information on the person in charge, department, and position stored in the memory 211. If the number of people available to handle the task is one, the processor 212 automatically assigns the relevant person as the person in charge (S305) and ends this processing flow. On the other hand, if the number of people available to handle the task is zero, the processor 212 selects no assignment (S306) as automatic assignment to the task is not possible, and ends this processing flow.

When there are multiple applicable persons calculated taking into consideration the department and position, the processor 212 determines whether the person with the most number of persons in the history of work related to the related tasks related to the task selected in S301 is limited to one person (S303). Specifically, the processor 212 counts the target persons based on the information of the person in charge, including the work history, stored in the memory 211. When there is only one applicable person, the processor 212 automatically assigns that person as the person in charge (S305), and ends this processing flow.

After that, when there are multiple suitable individuals after taking into account the history of work on related tasks, the processor 212 narrows it down to one specific person by making a comprehensive judgment of the applicable individuals' job titles, other work history, the content of the related tasks, etc. Then, the narrowed down applicable individuals are automatically assigned as the person in charge (S306), and this processing flow ends. For example, by setting weights in advance for the job titles, other work history, and related tasks, the processor 212 may extract the most suitable individual as the suitable individual based on the numerical values related to the weights, or may simply select an employee with a high job title. Furthermore, the accuracy of the comprehensive judgment may be improved using techniques such as machine learning or deep learning.

The above-mentioned flow for automatically allocating personnel is merely one example, and additional judgment items may be added, or some judgment items may be deleted. For example, automatic allocation of personnel may be performed by comprehensively judging department, position, and past history of work, without taking into account judgments regarding related tasks.

Next, the process flow executed by the server device 200 for the process related to registering a new task, etc., shown in FIG. 6B will be specifically described.

FIG. 7C is a diagram showing a process flow executed in the server device 200 according to an embodiment of the present disclosure. The process flow is mainly performed by the processor 212 of the server device 200 reading and executing a program stored in the memory 211.

According to FIG. 7C, the processor 212 refers to the operation task management table and reads out information on each task ID and the change date associated therewith. The processor 212 then judges whether or not there is any task among the read out tasks for which a predetermined period has passed since the change date. As a result, if it is judged that there is no task for which a predetermined period has passed since the change date (S401: No), this processing flow ends. On the other hand, if it is judged that there is a task for which a predetermined period has passed (S401: Yes), the processor 212 extracts the task ID of the task as the task for which the current operation status is to be confirmed (S402). The processor 212 then transmits a confirmation request to the terminal device 100 via the communication interface 214, in association with the task ID of the extracted task, to confirm the current operation status of the task (S403). The confirmation request transmitted here is as described in FIG. 6B and FIG. 8D.

Next, the processor 212 judges whether or not new task information related to a new task input by the user by a confirmation request in the terminal device 100 has been received (S404). The new task information is as described in FIG. 6B. If the new task information has not been received (S404: No), the processor ends this processing flow. On the other hand, if the new task information has been received (S404: Yes), the processor 212 generates new task ID information and stores it in the assignment task management table (S405). At this time, the processor 212 further stores the date on which the new task was generated as the indication date in association with the stored new task. Next, the processor 212 creates a dashboard for each task stored in the assignment task management table including the stored new task (S406). Specifically, data for drawing the assignment management screen shown in FIG. 8F is generated so that the screen can be displayed on the display of the terminal device 100 or the like. Then, the processor 112 transmits, via the communication interface 214, to the terminal device 100, a message indicating that the new task has been registered in the assignment task management table, and operation management information including data for drawing the assignment management screen. This ends the series of processing flows.
8. Other
Here, for example, in a listing examination, a securities company, an auditing firm, or the like may conduct a mock examination or a check of progress (so-called a short review). In the processing system 1 according to the present disclosure, each company can conduct a mock short review in advance when conducting such a mock examination or a check of progress. For example, when an implementation request for conducting a mock short review is received by the terminal device 100, the terminal device 100 transmits the implementation request to the server device 200 via the communication interface 114. When the implementation request is received by the server device 200, the processor 212 of the server device 200 refers to the maintenance task management table, the operation task management table, and the problem task management table, and generates the progress status of each task from the status of each task specified in the implementation request. For example, the processor 212 lists each task on a line for multiple tasks specified in the implementation request, and outputs various information on the person in charge, the progress status, the start date, and the end date for each task as a list. In this way, by performing an output simulating a short review in advance, it is possible to take measures in the short review more efficiently.

As described above, in this embodiment, it is possible to provide a new processing device, processing program, and processing method for tasks related to screening to grant specified qualifications to companies.

9. Modifications In the above-described embodiment, it is assumed that the set specified due date will not be changed, but the specified due date may be changed during the work of each task. In this case, the specified due date is reset and the schedule creation process is carried out again. Even in such a case, since an offset value is set for each task, the end date of each task can be easily set by subtracting the offset value from the specified due date, and further, a schedule can be easily created again taking into account holidays such as Saturdays and Sundays. In addition, at this time, the work period of the completed task may be taken into account and a schedule for the uncompleted task may be created.

In the above embodiment, the end date of each task is set by subtracting the offset value set for each task from the specified due date, and the work period for each task is set from the end date and the standard work period of each task, but the method of setting the work period is not limited to this. Specifically, the start date, which is the start deadline for each task, may be set by subtracting the offset number of days set for each task from the specified due date, and the work period for each task may be set from the start date and the standard work period of each task. In other words, if a numerical value that includes the standard work period is set in the offset value, the work period for each task may be set after the scheduled start date of each task is set. In other words, the work period for a task may be set based on the start date, which is the deadline for starting the task. Even in such a case, since an offset value is set for each task, the end date of each task can be easily set by subtracting the offset value from the specified due date, and it is also easy to re-create a schedule that takes into account holidays such as Saturdays and Sundays.

The processes and procedures described in this specification can be realized not only by those explicitly described in this disclosure, but also by software, hardware, or a combination of these. Specifically, the processes and procedures described in this specification are realized by implementing logic equivalent to the processes in a medium such as an integrated circuit, volatile memory, non-volatile memory, magnetic disk, optical storage, etc. In addition, the processes and procedures described in this specification can be implemented as computer programs and executed by various computers including terminal devices and server devices.

Even if the processes and procedures described herein are described as being executed by a single device, software, component, or module, such processes or procedures may be executed by multiple devices, multiple software, multiple components, and/or multiple modules. Furthermore, even if the various information described herein is described as being stored in a single memory or storage unit, such information may be stored in multiple memories provided in a single device or multiple memories distributed across multiple devices. Furthermore, the software and hardware elements described herein may be realized by integrating them into fewer components or by breaking them down into more components.

100 Terminal device 200 Server device (processing device)

Claims (10)

A processing device having at least one processor for creating a schedule of a plurality of tasks related to items to be evaluated in an audit of a company, the processing device comprising:
The at least one processor:
When receiving deadline information on when the review is scheduled, a start deadline or an end deadline of a work period for each of the plurality of tasks is set based on the deadline information;
setting a work period for each of the tasks based on the set start deadline or end deadline and a standard work period set for each of the tasks;
outputting the work period set for each of the plurality of tasks for each of the plurality of tasks;
a processing unit configured to perform processing for: The processing device according to claim 1, wherein the examination is an examination related to trading of securities issued by the company. The processing device according to claim 1, wherein the examination is conducted when the company is newly listed on a stock exchange. The processing device according to claim 1, wherein the at least one processor assigns a person in charge to each of the plurality of tasks. The processing device according to claim 4, wherein the person in charge is assigned based on the department and position of the person in charge. The processing device according to claim 4, wherein the person in charge is assigned based on related task information indicating that the tasks are related to each other among the plurality of tasks. The at least one processor:
storing status information indicating a status of each of the plurality of tasks;
determining whether a predetermined period of time has elapsed since the completion of each of the plurality of tasks based on the status information;
when the predetermined period has elapsed, outputting a confirmation request for requesting confirmation of the current status of the task for which the predetermined period has elapsed;
The processing device of claim 1 . The processing device according to claim 7, wherein when new task information regarding a new task is received based on the confirmation request, the received new task information is registered as a new task. A computer having at least one processor for executing a process for creating a schedule of a plurality of tasks related to items to be evaluated in an audit of a company, comprising:
When receiving deadline information on when the review is scheduled, a start deadline or an end deadline of a work period for each of the plurality of tasks is set based on the deadline information;
setting a work period for each of the tasks based on the set start deadline or end deadline and a standard work period set for each of the tasks;
outputting the work period set for each of the plurality of tasks for each of the plurality of tasks;
A processing program that makes it function as follows. A processing method executed by at least one processor in a computer having the at least one processor for executing a process for creating a schedule of a plurality of tasks related to items to be evaluated in an audit of a company, the method comprising:
receiving deadline information for when the review is scheduled, and setting a start deadline or an end deadline for a work period for each of the plurality of tasks from the deadline information;
setting a work period for each of the tasks based on the set start deadline or end deadline and a standard work period set for each of the tasks;
outputting the work period set for each of the plurality of tasks for each of the plurality of tasks;
A processing method comprising:

Images