JP7489009B1 - Administrative business management system, administrative business management method, administrative business management program - Google Patents

Abstract

The present invention provides a technology that supports efficient management and operation of administrative work flows. The present invention accepts registration of business information related to business activities established based on laws and regulations, acquires action history associated with the business information, and outputs action status for the business activities based on the action history. [Selected Figure] FIG.

Description

Application of Article 30, Paragraph 2 of the Patent Act February 9, 2023 online, February 21, 2023 Takahama City Hall, March 2, 2023 online, March 3, 2023 Minamioguni Town City Hall, March 24, 2023 Kumamoto City Hall, March 27, 2023 Tsukubamirai City Hall, April 18, 2023 Osaka Prefectural Office, April 20, 2023 Ishikawa Prefectural Office, April 20, 2023 Online on April 24th, 2020, Toyonaka City Hall on April 28th, 2023, Shinagawa Ward Office on May 26th, 2023, Wakayama Prefectural Office on June 20th, 2023, Fujisawa City Hall on July 27th, 2023 , July 31, 2023 Online, Reiwa Wakayama Prefectural Office on August 4, 2023, Kitakyushu City Hall on August 31, 2023, Shiga Prefectural Office on September 20, 2023, Ota Ward Office on September 25, 2023, and September 28, 2023 Fukui Prefectural Office, September 29, 2023 Toyama Prefectural Office, October 4, 2023 Online, October 4, 2023 Mie Prefectural Office, October 6, 2023 NTT Data Hokuriku Corporation, The information sessions were held at the Ishikawa Prefectural Office on October 6, 2023, the Miyagi Prefectural Office on October 10, 2023, the Meguro Ward Office on October 11, 2023, and the Miyazaki Prefectural Office on October 20, 2023.

Article 30, paragraph 2 of the Patent Act applies. August 10, 2023. Disclosure via the website at <URL: https://corp. wise-vine. com/service> and <URL: https://corp. wise-vine. com/recruit>

Application of Article 30, Paragraph 2 of the Patent Act. Disclosure by email to the Reconstruction Agency on March 23, 2023, the General Incorporated Association of Passionate Regional Revitalization Ventures on October 30, 2023, and Trust Bank Co., Ltd. on October 31, 2023.

The present invention relates to an administrative business management system, an administrative business management method, and an administrative business management program.

In the finances of local governments and other organizations, budgets are compiled from limited financial resources and used to implement projects. Local governments and other organizations handle a wide variety of administrative tasks and projects, and in order to compile budgets efficiently for these tasks and projects, it is necessary to properly evaluate each task and project.

Patent Document 1 discloses a technology that can efficiently support local governments introducing an administrative evaluation system in setting administrative evaluation indicators that match the characteristics of the local government. Specifically, Patent Document 1 discloses a technology that includes a step of registering the local government characteristics of a local government that is newly introducing an administrative evaluation system in a local government characteristic database, a step of accepting a designation of the administrative business of the local government, and for a local government whose value of the local government characteristic for generating candidate indicators for the accepted administrative business is close to the value of the registered local government characteristic, reading out from the administrative evaluation indicator database a performance indicator level corresponding to the indicator of the administrative business, generating administrative evaluation candidate indicator information that stores the performance indicator level, and a step of outputting the generated administrative evaluation candidate indicator information.

Patent Document 2 discloses a technology for simplifying the processes of the financial department involved in budget assessments and administrative reform plans, and for realizing budget assessments and long-term financial estimates that are in line with the actual circumstances of each business. Specifically, Patent Document 2 discloses a technology that includes a plan value aggregation process for each business that aggregates the annual planned values of costs and financial resources entered into the business sheet, an estimate calculation process for calculating estimates for each expense item based on objective estimates for business items that do not create revenue information or business sheets, a specific expense item estimation process for making estimates for specific expenses, an estimation method selection process for selecting an estimation method to be executed for each revenue and expenditure item, and a medium- to long-term financial outlook estimation process for estimating a medium- to long-term financial outlook based on the plan for each individual business from the estimation results based on the method selected in the estimation method selection process.

JP 2002-334185 A JP 2005-293321 A

Administrative work flows are complex, making it difficult to manage and operate them efficiently. In addition, administrative tasks and projects carried out by administrative agencies have different budget preparation methods and jurisdictions depending on the priority of the task or project, and this has led to an issue of rising costs in managing and operating them.

The present invention was made in consideration of the above-mentioned problems, and the problem to be solved is to provide technology that supports the efficient management and operation of administrative work flows.

In order to solve the above-mentioned problems, the present invention provides an administrative business management system comprising a business registration unit, a behavior history acquisition unit, and a behavior status output unit, the business registration unit accepts registration of policy system information related to at least policies, measures, and business affairs established based on laws and regulations, the behavior history acquisition unit acquires behavior history related to the policy system information, and the behavior status output unit outputs behavior status related to the policy, the measure, or the business affairs based on the behavior history.

The present invention also provides a method for managing administrative operations, in which a computer executes the steps of accepting registration of policy system information relating to at least policies, measures, and business operations enacted based on laws and regulations, acquiring behavioral history related to the policy system information, and outputting behavioral status related to the policy, measure, or business operations based on the behavioral history.

The present invention also provides an administrative business management program that causes a computer to function as a business registration unit, a behavior history acquisition unit, and a behavior status output unit, the business registration unit accepting registration of policy system information related to at least policies, measures, and business affairs established based on laws and regulations, the behavior history acquisition unit acquiring behavior history related to the policy system information, and the behavior status output unit outputting behavior status related to the policy, the measure, or the business affairs based on the behavior history.

This configuration makes it possible to support efficient management and operation of business operations by outputting behavioral status related to business operations based on behavioral history related to the business operations.

In a preferred embodiment of the present invention, the behavioral history includes approval behavior for the business, the behavioral status includes an approval status for the business, and the behavioral status output unit outputs the approval status for the business based on the approval behavior.
In a preferred embodiment of the present invention, the behavioral status output unit outputs an approval status including the number of approvals or the approval achievement rate in a group to which a plurality of tasks and projects belong.
With this configuration, the status of approval actions for business operations can be output, thereby supporting efficient management and operation of business operations.

In a preferred form of the present invention, the behavioral history includes a pointed out behavior regarding the business, and the behavioral history acquisition unit acquires the pointed out behavior by accepting posted data in association with a pointed out element regarding the business, and acquires the approval behavior by accepting posted data in association with an approval instruction corresponding to the pointed out behavior.
With this configuration, it is possible to smoothly acquire a behavior history through the exchange of posted data.

In a preferred form of the present invention, the behavioral history includes commenting behavior, and the behavioral history acquisition unit acquires the commenting behavior by accepting posting data in association with a comment corresponding to the pointed-out behavior, and the behavioral status output unit outputs a behavioral status showing an icon of the actor in a time series chart based on the behavioral history including the pointed-out behavior, the commenting behavior, and the approval behavior, and information indicating the actor who performed the behavioral history.
In a preferred embodiment of the present invention, the time series chart starts with the indicated behavior and ends with the approval behavior.
With this configuration, the progress of action history for business operations can be output as a chart, providing a suitable user interface for more efficiently grasping the status of business operations.

In a preferred embodiment of the present invention, the behavioral history includes execution actions for the business, the behavioral status includes an execution status for the business, and the behavioral status output unit outputs the execution status of the business based on the execution actions.
In a preferred embodiment of the present invention, the action status output unit receives input of a budget correction instruction in association with at least one execution action, generates the execution status, and outputs it as a notice to an execution manager.
With this configuration, the management and operation of the situation regarding the execution of administrative tasks and projects can be made more efficient.

In a preferred form of the present invention, the behavioral history includes behavioral history for key business projects and behavioral history for general business projects, the behavioral status includes behavioral status for the key business projects and behavioral status for the general business projects, and the behavioral status output unit outputs the behavioral status for each of the key business projects and the general business projects based on the behavioral history for each of the key business projects and the general business projects.
In a preferred form of the present invention, the behavioral history includes budget preparation actions for preparing a key budget for the key business and a general budget for the general business, and approval actions for the key business and the general business, and the behavioral history acquisition unit acquires the budget preparation actions and approval actions for the key business, and generates a notification for acquiring the budget preparation actions and approval actions for the general business.
This configuration makes it possible to support the unified and efficient management and operation of administrative work flows that differ between priority business operations and general business operations.

In a preferred form of the present invention, the behavioral history includes a raising action that raises an issue based on factors for response or execution, and a policy, measure, or business based on the issue, and the behavioral status output unit outputs the process related to the establishment of the issue or the policy, measure, or business as a raising status based on the raising action and the designation of the issue or the policy, measure, or business.
This configuration makes it possible to efficiently manage and operate issues that arise during administrative work flows and the series of situations surrounding administrative tasks and projects.

The present invention provides technology that supports the efficient management and operation of administrative work flows.

FIG. 1 is a system configuration diagram of the present embodiment. FIG. 2 is a diagram showing the hardware configuration of the present embodiment. 3 is a process flowchart of the present embodiment. 4 shows an example of a data configuration according to the present embodiment. 13 shows a display example of a group management screen according to the embodiment. 13 shows a display example of a progress information creation screen and an instruction notification according to the embodiment. 13 shows a display example of a group formation screen according to the present embodiment. 13 shows a display example of a group formation screen according to the present embodiment. 13 is a display example of a budget allocation registration screen according to the embodiment. 4 is a process flowchart of the budget compilation stage of the present embodiment. 13 shows a display example of a tag processing screen according to the embodiment. FIG. 4 is a schematic diagram of tag information according to the embodiment. 2 shows an example of the configuration of a classification model according to the present embodiment. 13 shows a display example of a comparison evaluation screen according to the present embodiment. 13 shows a display example of a matching screen according to the embodiment. Block diagram of implementation example 2. An example of behavioral history data structure. Processing sequence of implementation example 2. 13 is a process flowchart of implementation example 2. An example of the screen display regarding pointed out actions. An example of the chat screen. An example of the chart screen. An example of the execution management screen.

The following describes the administrative business management system, method, and program of the present invention with reference to the drawings. Note that the embodiment shown below is an example of the present invention, and the present invention is not limited to the embodiment below, and various configurations can be adopted.

In this embodiment, the configuration, operation, etc. of the administrative project management system will be described, but similarly configured methods, devices, computer programs, and program recording media storing such programs can also achieve similar effects. The series of processes according to this embodiment described below is provided as a computer-executable program, and can be provided via a non-transitory computer-readable recording medium such as a CD-ROM or flexible disk, or even via a communication line.

The administrative business management system is composed of a computer device. The computer device has an arithmetic device such as a CPU (Central Processing Unit) and a storage device. The computer device can function as an administrative business management device by executing an administrative business management program stored in the storage device using the arithmetic device. The administrative business management method is realized by processing of the computer device including the administrative business management device.

In this embodiment, the administrative business management system is used in an administrative organization. An administrative organization is an organization that manages administration, including government agencies, ministries, and public organizations such as the national and local governments.

In this embodiment, a policy indicates the direction and purpose of urban development in the administrative division (city, ward, town, village, etc.) in which it is established. A measure indicates the method for realizing the policy. An administrative project indicates more specific means for realizing the policy. An administrative project is implemented by each bureau belonging to the administrative division based on the budget of each bureau. Note that the classification of policies, measures, administrative tasks, etc. is not limited to these, and further classifications such as detailed measures may be established.

In this embodiment, the main explanation is about a mechanism for supporting administrative work at each stage of a business project, such as the planning stage, budget preparation stage, execution stage, and evaluation stage, using an administrative project management system. In the planning stage, a plan for the business project to be implemented in the execution year (e.g., the following year) of the target business project is prepared. In the budget preparation stage, a budget request for the business project related to the plan is prepared, and a financial assessment of the budget request is carried out. In the execution stage, business projects that have passed the assessment are executed. In the assessment stage, an administrative assessment report for the executed business project is prepared. Note that each of the above-mentioned stages is merely an example, and the number and contents of the stages are not limited.

<System Configuration>
Fig. 1 shows a system configuration diagram of the administrative business management system 1. As shown in Fig. 1, the administrative business management system 1 includes an administrative business management device 2, a user terminal 3, a request destination terminal 4, and a storage unit DB, and each component is connected to a communication network NW and configured to be able to communicate with each other.

<Administrative business management device: Implementation example 1>
The administrative business management device 2 includes, as functional components, a business registration unit 21, a group registration unit 22, a tag processing unit 23, an evaluation unit 24, an update unit 25, a search processing unit 26, and a matching processing unit 27.

The user terminal 3 is a terminal device operated by a user at each office of an administrative division such as a local government. Although only one user terminal 3 is shown in FIG. 1, multiple user terminals 3 are installed in each local government. Also, there may be multiple local governments.

In this embodiment, users include financial officers of each bureau, original section personnel, general affairs managers, etc. Original section personnel perform tasks such as creating business plans, creating budget requests, and creating administrative evaluation reports. Financial officers perform financial-related tasks such as requesting original section personnel to create budget requests and evaluating budget requests. Managers perform tasks such as selecting key projects based on plans, prioritizing, and assessing budget requests approved by financial officers. The administrative business management system 1 provides each user with specific operating authority and controls the permission and restriction of specific functions according to the operating authority.

The request destination terminal 4 is a terminal device operated by a party to whom the government has entrusted an administrative task or business or requested collaboration. In this embodiment, the request destination includes private companies, other local governments, etc. Although only one request destination terminal 4 is shown in FIG. 1, there may be multiple request destination terminals.

The storage unit DB is a database and is not limited to the configuration shown in FIG. 1, so long as it is configured to be capable of data communication with the administrative business management device 2. The storage unit DB may be, for example, built into the administrative business management device 2, or installed outside the administrative business management device 2 and connected for communication via a wire. The storage unit DB stores data configured to uniquely identify various types of information using identification information specific to each type of information, such as an ID, as a key.

Figure 2(a) shows a hardware configuration diagram of the administrative business management device 2. The administrative business management device 2 has a control unit 201, a memory unit 202, and a communication unit 203 as its hardware configuration. In this embodiment, the administrative business management device 2 can use a computer device such as a server or a personal computer. Note that the administrative business management device 2 may be composed of multiple computer devices, and is not limited to the configuration shown in Figure 2(a) as long as it can realize the above-mentioned functional components (21-27) as a whole.

The control unit 201 is composed of one or more processors such as a CPU, and controls the overall processing in the administrative business management device 2 by executing the administrative business management program, OS (Operating System), and other applications. The memory unit 202 is a hard disk drive (HDD), solid state drive (SSD), flash memory, RAM (Random Access Memory), etc., and stores the administrative business management program and various data. The communication unit 203 controls communication with the communication network NW, and realizes data communication with the user terminal 3, the request destination terminal 4, and the memory unit DB. The control unit 201 causes the computer to function as the administrative business management device 2 by executing the administrative business management program.

FIG. 2(b) shows a hardware configuration diagram of a terminal device 9 including a user terminal 3 and a request destination terminal 4. The terminal device 9 includes, as its hardware configuration, a control unit 901, a storage unit 902, a communication unit 903, an input unit 904, and a display unit 905. In this embodiment, the terminal device 9 may be a smartphone, a personal computer, a tablet terminal, or the like.

The control unit 901 is composed of one or more processors such as a CPU, and controls the overall processing in the terminal device 9 by executing an OS and other applications. The storage unit 902 is a HDD, SSD, flash memory, RAM, etc., and stores a browser application and various data. The communication unit 903 controls communication with the communication network NW, and realizes data communication with the administrative business management device 2. The input unit 904 is an input interface that accepts operation requests from the operator, and is composed of a touch panel, mouse, keyboard, etc. The display unit 905 is composed of a display that displays the processing results by the control unit 901, etc.

Figure 3 shows the process flow for the planning, budgeting, execution, and evaluation stages of an administrative project. The administrative project management system 1 provides a platform for managing each stage of an administrative project, such as the planning, budgeting, execution, and evaluation stages. The progress of an administrative project is managed by the progress status associated with the administrative project information.

At the planning stage, a business plan is created related to the tasks and businesses to be executed in the following fiscal year. When planning a new task and business (YES in S11), the business registration unit 21 accepts the registration of task and business information and stores it in the memory unit DB (S12). The business registration unit 21 creates a business plan for the following fiscal year based on the task and business information, and registers it in association with the task and business information (S13). Note that if there are existing tasks and businesses (NO in S11), a business plan for the following fiscal year is created based on the existing task and business information, and registers it in association with the task and business information (S13).

The administrative business management device 2 accepts a budget request operation including budget information created in response to the business information (S14). The update unit 25 updates the progress status from before request to requested in response to the budget request operation. When the update unit 25 accepts an approval operation for the budget request via the user terminal 3 of the financial officer (YES in S15), it updates the progress status of the business information to assessed (S16). When the update unit 25 accepts an operation to disapprove the budget request via the user terminal 3 of the financial officer (NO in S15), it updates the progress status of the business information to disapproval or before request. If the budget request operation is disapproved, the update unit 25 may output a request to amend the budget information to the user terminal 3 and accept a budget request operation including the amended budget information again. In addition, in the budget compilation stage, the update unit 25 may further update the progress status to final assessment by accepting an approval operation for the budget request via the user terminal 3 of the administrator.

In the execution stage, the progress status of the administrative business information is updated to the execution stage, and the administrative business is executed. Here, the progress status is automatically updated when the execution year arrives, or is updated by an update operation on the user terminal 3. The administrative business management device 2 may appropriately accept an input operation of performance information of the administrative business information via the user terminal 3. When the execution of the administrative business is completed, the update unit 25 updates the progress status to the evaluation stage. Here, the progress status is automatically updated when the execution deadline passes, or is updated by an update operation on the user terminal 3.

In the evaluation stage, an administrative evaluation report is created related to the completed administrative business. The evaluation unit 24 accepts an input operation to associate evaluation information with administrative business information via the user terminal 3, and stores it in the memory unit DB (S18). When the evaluation stage is completed, planning information, budget information, evaluation information, etc. are associated with the administrative business information, and the existing administrative business information can be used when creating a business plan related to the administrative business to be executed in the following year. The administrative business management device 2 can repeat the process from S11 when managing administrative business for the following year.

<Business Registration Department>
The business registration unit 21 accepts registration of business information related to business established based on laws and regulations via the user terminal 3, and stores the information in the storage unit DB. The business information may be acquired from a database installed in each local government.

Figure 4 shows an example of the configuration of business and administrative business information and various information associated with the business and administrative business information. As shown in Figure 4 (a), the business and administrative business information has basic information, business group information, tag information, progress status, planning information, budget information, evaluation information, etc., with a business ID for identifying the business and administrative business as a key. The various information included in the business and administrative business information is identified by its respective ID.

The basic information includes the local government ID, the name of the business/project, a project overview, the planned execution year, the name of the department, the name of the subdivision, etc. The planned execution year indicates the number of years or the fiscal year for which execution is planned.

As shown in FIG. 4(b), the plan information has the execution year, plan outline, evaluation items, goals for the evaluation items, etc., with the plan ID as a key. The plan information is created as a business plan prepared for each execution year, and is stored in the memory unit DB in association with the business information.

Evaluation items include quantitative evaluation items and/or task evaluation items. Each evaluation item has a set goal, and is evaluated based on the achievement of that goal.

Quantitative evaluation items are evaluation items that can be quantitatively evaluated using numerical values, etc., and include KPIs and KGIs. For example, for an administrative project related to "securing agricultural workers," "number of agricultural workers" is set as a quantitative evaluation item, and a specific number is set as the target for the quantitative evaluation item. The progress of the target is evaluated based on the actual results against the set target. Multiple quantitative evaluation items may be set.

Task evaluation items are evaluation items that can be evaluated based on the achievement of a set task. Task evaluation items are set as arbitrary task names or task contents, and a schedule for carrying out the task is set as a goal for the task evaluation item. The achievement status of the goal is evaluated based on the actual results against the set goal. The achievement status of a task evaluation item is input as whether the task was completed, whether the task was completed within the schedule, etc. Multiple task evaluation items may be set. Furthermore, important tasks may be set as task evaluation items from the set tasks, and the achievement status of the goals of important tasks and normal tasks can be evaluated.

As shown in FIG. 4(c), the budget information has the execution year, budget amount, revenue amount, etc., with the budget ID as a key. The budget information is finalized when the budget request for the target year is approved, and is stored in the memory unit DB in association with the business information. The budget amount indicates the amount of expenses for executing the business. The revenue amount indicates the amount of financial resources, etc., for executing the business. The revenue amount may include amounts broken down into financial resources such as general financial resources, specific financial resources, mandatory budgets, priority budgets, and management budgets. The revenue amount is allocated to each business from the organization's total financial resources by referring to a financial resources database (not shown) for the organization in the execution year.

The business group information has a total budget and total revenue based on the budget information. The total budget is the total budget amount of the affairs and businesses that belong to the group. The total revenue is the total revenue amount of the affairs and businesses that belong to the group.

As shown in FIG. 4(d), the budget limit information has the execution year, business group ID, budget limit amount, etc., with the budget limit ID as a key. The budget limit information is set by the financial officer when submitting a budget request for the target execution year. In this embodiment, the budget limit amount is set to make up for the difference between the total budget amount and the total revenue in the business group. The budget limit information may have a data structure that can directly or indirectly reference the business group ID, and may be associated with a progress ID, for example.

As shown in FIG. 4(e), the evaluation information has an evaluation ID as a key, an execution year, and actual results. The actual results include quantitative evaluation results corresponding to quantitative evaluation items and task evaluation results corresponding to task evaluation items. The quantitative evaluation results are actual values against target values such as KPIs and KGIs, and the task evaluation results are whether or not each task has been achieved, and the number of tasks that have been achieved. The actual results may be input as appropriate at the execution stage of the business or project. The quantitative evaluation results may include the amount of expenditure required for the execution of the business or project in question. The administrative evaluation report for the business or project in the target year may be stored in the memory unit DB in association with the evaluation information.

<Progress management>
In this embodiment, the planning, budgeting, execution, and administrative evaluation of the next fiscal year's business projects are managed by progress information generated by category. Furthermore, progress information is generated by business group consisting of multiple business projects, and the progress of each business group is managed.

Figure 5 (a) shows an example of the screen display of the group management screen W1 displayed on the user terminal 3. The group management screen W1 has a summary display section W11, a group list display section W12, and a new creation button W13. The progress information is used for planning, budgeting, and execution of the next fiscal year's administrative business or business group's business, as well as for managing the progress of each task, such as administrative evaluation.

The summary display section W11 displays the status of setting the frame, the frame amount, and the requested amount. The frame indicates the frame for the amount that can be requested for the budget. In the example of Figure 5 (a), it displays the number of tasks and projects that are subject to the frame before the budget request and the ratio of the number of tasks and projects that have been requested and have a frame set, the ratio of the total budget and the requested budget, and the ratio of the assumed budget and the requested budget for each budget classification such as the mandatory budget, the priority budget, and the management budget.

The group list display unit W12 displays a list of business group information. Based on the business group information and various information associated with the business group information, the group list display unit W12 also displays a list of group ID, business group name, person in charge, progress, category, deadline, total business amount, and budget. The progress status displays the evaluation results regarding the progress status for each progress status stage. The evaluation results regarding the progress status are output based on the total number of administrative tasks and projects belonging to the business group and the quantity of administrative tasks and projects having a specified progress status.

When the new group creation button W13 receives an input operation, it displays the group creation screen W2 on the user terminal 3, as shown in FIG. 5(b).

The group creation screen W2 includes a group information input section W21 and a registration button W22. In this embodiment, the registration of a business group name and category is accepted as business group information. The category is selected from planning, budgeting, execution, administrative evaluation, etc. When the registration button W22 is pressed, a request to register the information entered in the group information input section W21 as business group information is sent to the administrative business management device 2.

As shown in FIG. 4(f), the business group information has a business group name and the business ID of one or more administrative businesses associated with the business group, with the business group ID as a key. The business group information may also include categories to be managed. Here, the business group information may be in a form in which an evaluation axis corresponding to the category is associated with the business group information. The evaluation axis is used by the evaluation unit 24 to select an evaluation target.

In one embodiment, the business group information is configured so that the user can register any administrative or business information in association with it. The group name of the business group information is determined according to the classification conditions set by the user. Here, the classification conditions include a category selected by the user. In addition to the category, the classification conditions may include any classification conditions appropriate to the purpose of the grouping set by the user.

As a specific example, when creating a group for organizing budgets for departments and sections, the business group information has the category set to budget organization and a group name such as "Ministry of Agriculture, Forestry and Fisheries at the beginning of fiscal year x." When creating a group for organizing priority tasks and projects, the business group information has a group name such as "City X's priority projects in fiscal year x." The group name is preferably a name that allows one to guess the tasks and projects that may be associated with the business group, and may also be associated with a message indicating the purpose of grouping and rules regarding group organization.

In one aspect, the business group information and the administrative and business information each have classification conditions. The business group information is configured to be automatically registered in association with administrative and business information to which similar classification conditions have been assigned. The memory unit DB stores master information of the classification conditions. The administrative and business information is associated with the business group information by referring to the master information and selecting a classification condition. Note that multiple classification conditions may be set for one business group or one administrative and business information. Furthermore, the classification conditions may correspond to tag information, which will be described later.

As a specific example, the master information has classification conditions such as item classification, policy/measure/business classification, settlement statistics/purpose classification, organization classification, and nature classification. Item classification is a classification related to the breakdown of revenue or expenditure, and has subclassifications such as property expenses, public works, personnel expenses, and subsidy grants. Policy/measure/business classification is a classification indicating whether the classification target is a policy, a measure, a sub-measure, or an administrative project, and has subclassifications such as specific policy names, measure names, and administrative project names. Settlement statistics/purpose classification is a classification related to settlement statistics or purposes, and has subclassifications such as specific settlement statistics names and types of purposes. Organization classification is a classification such as departments and sections in an organizational chart, and has subclassifications such as specific department names and section names. Nature classification is a classification related to the breakdown of revenue or expenditure, and has subclassifications such as property expenses, public works, subsidies, and prefectural management, personnel expenses, and subsidies and subsidy grants. Note that classification conditions are not limited to these and may be set appropriately depending on the purpose.

Figure 6 shows an example of the screen display of the progress information creation screen W3. The progress information creation screen W3 includes a progress information input section W31 that accepts an instruction operation to input progress information, and a registration button W32 that is pressed when registering/updating the progress information input in the progress information input section W31. In this embodiment, the progress information creation screen W3 transitions by accepting a selection operation on the three-dot leader in the group list display section W12, and can generate progress information for the business group. The progress information input section W31 may generate progress information for the business group by accepting a selection operation of a business group based on registered business group information, or generate business group information and progress information by accepting an input operation of a new business group name.

When the registration button W32 is pressed, an instruction to register the progress information is sent to the administrative project management device 2. The administrative project management device 2 stores the progress information in the memory unit DB.

The progress information is used to manage the progress of administrative projects belonging to a business group. As shown in FIG. 4(g), the progress information has a progress name, a business group ID, a person in charge, a schedule, a message, etc., with a progress ID as a key. The message is text data regarding instructions to the person in charge, and can include, for example, instructions for group formation and deadlines.

When the group registration unit 22 receives an instruction operation including the person in charge regarding the business group information via the progress information creation screen W3, it generates an instruction notification including access information to the business group information and outputs it to the person in charge by referencing the notification destination.

Figure 6 (b) shows an example of an instruction notification sent to a person in charge. The instruction notification includes a progress information message and a link (access information) such as a URL to a group organization screen for a business group identified by a business group ID. The notification is sent to the person in charge's email address or person in charge ID, for example. The person in charge who receives the instruction notification can access the group organization screen and organize the business group.

When the progress information is registered, the evaluation unit 24 executes an evaluation process using the progress status as an evaluation axis, based on the business group information associated with the progress information and the progress status of the administrative business information associated with the business group information. The update unit 25 updates the progress status according to the submission status of the business plan at the planning stage, the submission status of the budget request at the budget compilation stage, the achievements and task completion status for the evaluation items at the execution stage, the submission status of the administrative evaluation report at the administrative evaluation stage, and the like. The evaluation unit 24 can tally up the progress status of the administrative business belonging to the business group by stage, and output the evaluation results regarding the progress status of each administrative business relative to the entire business group. The tally up results of the progress status are shown, for example, by the percentage or total number by status. The evaluation results regarding the progress status are reflected in the progress status in the group list display unit W12. This makes it easy to grasp the progress status in each business group as a list.

The progress status of administrative business information is a status that indicates the processing stage according to the category. The progress status in the planning stage is further classified into detailed stages such as before the business plan is submitted and after it has been submitted. The progress status in the budget preparation stage is further classified into detailed stages such as before the budget request is requested, after it has been assessed, etc. The progress status in the execution stage is further classified into detailed stages such as before execution, in execution, after it has been executed. The progress status in the evaluation stage is further classified into detailed stages such as before the administrative evaluation report is submitted and after it has been submitted. The progress status is updated by accepting setting operations via the user terminal 3 according to the processing stage.

<Group composition>
The business information is grouped by being associated with the business group information. In this embodiment, the business group can be defined as any group for the purpose of supporting suitable business planning and budget compilation, such as selecting business to be included or excluded so as to fit within a budget limit or selecting business based on past performance.

Figures 7 and 8 show examples of the group formation screen W4 displayed on the user terminal 3. The group formation screen W4 is displayed on the display unit 905 of the user terminal 3 by accessing it from a link to the business group in the instruction notification. The group formation screen W4 may also be displayed by pressing a details button on the group management screen W1. Here, an example is described in which, at the budget formation stage, a department employee who has received an instruction notification regarding a request to create a budget request document related to a certain business group performs operation input related to group formation, such as adding, changing, or deleting administrative tasks to be associated with the business group, while referring to the expected budget and past performance.

The group organization screen W4 includes a summary display section W41, a group organization section W42, a search section W43, and a business display section W44. The summary display section W41, the group organization section W42, and the search section W43 are each configured to be able to be switched between displayed and hidden using a pull-down menu. In the display example of FIG. 7, only the search section W43 is displayed, and in the display example of FIG. 8, only the summary display section W41 and the group organization section W42 are displayed.

The search unit W43 provides a function for searching for administrative tasks and business operations to be added, changed, or deleted from a business group. The search unit W43 accepts input of one or more search conditions. The search processing unit 26 executes a search process for the target administrative task and business information based on the search conditions. The search unit W43 can adopt a keyword input format, a condition selection format, or the like as the input format for the search conditions.

The search unit W43 can use as search criteria the execution year, business group, budget category such as initial budget or supplementary budget, specified keywords, classification conditions, tag names, past KPIs and budget-related results, etc. KPIs and budget-related results are set by specifying a specified period and the rate of increase or decrease of the KPI or budget, etc. The original department staff member refers to the instruction notice and selects the administrative business to be added, changed or deleted from the business group.

The search unit W43 can display the distribution status of classification conditions and tag information, such as the quantity of business operations associated with the classification conditions and tag names. It may also display the total number of business operations and information associated with the business group information at the current time, the total budget amount for the business group information, the total revenue, etc.

The business display unit W44 displays a list of business operations that are candidates for addition to the business group based on the business operation information acquired as a search result by the search processing unit 26. The add buttons W441A to W441C of the business display unit W44 accept the selection operation of the business operations to be added to the business group.

The candidate display section W421 of the group formation section W42 displays the administrative businesses that are candidates for the group selected by the add button W441. When the group creation button W422 is pressed, the administrative businesses displayed in the candidate display section W421 are registered as a business group. In addition, the group selection section W423 is configured as a selection tab, and by accepting the selection operation of an existing business group, it is possible to perform a bulk operation to add, change, or delete administrative businesses that belong to the business group.

The evaluation result display unit W411 displays the evaluation results of the business group. Here, the evaluation results include the total budget amount and average budget amount of the administrative projects belonging to the business group. The evaluation results can be displayed in a distinguishable manner, such as total budget amount and average budget amount by budget classification and progress status. Furthermore, the evaluation results may be displayed in a manner that allows comparison of the total budget amount, the budget amount of other business groups, the quota amount, etc. with the budget amount of the target business group.

The switching unit W412 can switch the evaluation axis by accepting a selection operation and update the evaluation result displayed in the evaluation result display unit W411. For example, the evaluation axis has a budget limit amount as an evaluation item and a target value corresponding to the evaluation item. The evaluation result is output based on the target value of the budget limit amount and the requested budget amount, which is the actual value. In FIG. 8, the target value is the budget limit amount per task and project belonging to the business group, and the actual value is the requested budget amount per task and project belonging to the business group. For example, when the requested budget amount exceeds the budget limit amount, the evaluation result display unit W411 may call attention to it by highlighting the text.

As one aspect, the evaluation result display unit W411 displays the total budget amount and the average budget amount for each business unit as the evaluation result. The total budget amount displays the total amount for each type of financial resource, such as general financial resources and specific financial resources. The average budget amount displays the average budget amount for each business type, such as new projects and priority projects.

In one embodiment, the evaluation result display unit W411 includes an average budget amount for each business unit and/or business group as an evaluation result. The average budget amount is output for each business unit and/or business group in accordance with the progress status of the budget preparation stage, i.e., unrequested, requested, and assessed.

The summary display unit W41 outputs evaluation results based on the administrative businesses belonging to the business group and the administrative businesses that are candidates for the group selected in the group formation unit W42. For example, when the administrative businesses that are candidates for the group are changed, such as by being added or deleted, the summary display unit W41 can display the evaluation results recalculated in response to the change. By providing at least the summary display unit W41 and the group formation unit W42 on the same screen, the group formation screen W4 becomes an interface that effectively supports selecting administrative businesses to associate with a business group while referring to the evaluation results.

<Budget Allocation Registration>
FIG. 9 shows an example of the screen display of the budget allocation registration screen W5 displayed on the user terminal 3. The budget allocation registration screen W5 is configured to be transitionable from the group organization screen W4. The budget allocation registration screen W5 includes a budget information display section W51, a budget allocation setting section W52, and a registration update button W53. The budget information display section W51 displays the business group name to which the budget allocation information is associated, the total revenue secured for the current business group, and the total budget required for the current business group. The budget information display section W51 refers to the budget information of the business business information associated with the business group information, and displays the total budget amount and the total revenue amount in the business group information calculated based on the budget amount and the revenue amount in the target year. When the business group is to be granted the budget allocation, the budget allocation setting section W52 accepts an operation input to set it to on and accepts a setting input of the budget allocation amount. The budget allocation setting section W52 may be configured to automatically input the difference between the total budget amount and the total revenue amount. When the register update button W53 is pressed, a request to register or update the budget allocation amount set and input in the budget allocation setting unit W52 as budget allocation information is sent to the administrative business management device 2. The group registration unit 22 accepts the registration of budget allocation information including the budget allocation amount based on the total budget amount and the total revenue amount linked to the business group information via the budget allocation registration screen W5, and stores it in the memory unit DB.

Figure 10 shows an example of the processing flow at the budget compilation stage. The administrative business management device 2 accepts a request to register progress information via the user terminal 3 of the financial person in charge (S21). In S21, the registration request may include a request to register business group information. When the progress information is registered, the administrative business management device 2 may output an instruction notification regarding a request for group formation and budget request creation to the user terminal 3 of the person in charge. The administrative business management device 2 accepts a registration request to associate budget allocation information with business group information via the user terminal 3 of the financial person in charge (S22). Note that the steps of S21 and S22 may be reversed. The original section person in charge selects the business business information to be associated with the business group information while referring to the budget information, budget allocation information, evaluation results of the summary display unit W41, past evaluation information, etc., to form a group. In addition, the original section person in charge creates budget information (budget request) for the execution year of each business business information while referring to the budget allocation information and evaluation results. The administrative business management device 2 receives, via the user terminal 3 of the original department staff, an instruction to register the business information to be associated with the business group information, and an instruction to register the budget information (S23). The financial staff and/or manager decides whether to approve or not approve the budget information by referring to the budget information, budget allocation information, evaluation results, past evaluation information, etc. The administrative business management device 2 receives, via the user terminal 3 of the financial staff and/or manager, an approval instruction regarding the budget information of each business information, thereby sequentially completing the processing of the budget compilation stage (S24). The progress status of each completed business is reflected as the progress of the business group, thereby realizing progress management by business group.

<Tag Information: Example 1>
The tag processing unit 23 associates the tag information with the task/business information and/or business group information and stores the tag information in the storage unit DB. The tag information is defined for the purpose of improving the searchability, identifiability, and ease of management of the task/business or business group to which it is categorized, by being assigned according to a unified rule. The tag information has a tag ID and a tag name, as shown in FIG. 4(h).

The tag information may further include a granularity level indicating whether the tagged object corresponds to a policy, measure, minor measure, administrative project, etc. In this embodiment, the tag information is configured, for example, as a hierarchical classification according to the granularity level. Tag information whose granularity level is a policy includes, for example, insurance and medical care, town development, logistics and transportation, administrative management, manufacturing, local companies, agriculture, forestry and fisheries, etc. Tag information whose granularity level is a measure includes, for example, enhancement of special needs education, development of sports facilities, support for local companies, support for small and medium-sized enterprises, and workers in the agriculture, forestry and fisheries industries. Tag information whose granularity level is an administrative project includes, for example, financing for small and medium-sized enterprises, distribution of subsidies, holding of local events, and workers in agriculture.

The granularity level is classified in the following order: policy, measures, and business operations. In other words, measures are a lower level than measures, and measures are a lower level than policies. Specifically, measures related to "agriculture, forestry, and fisheries" are enacted for policies related to "agriculture, forestry, and fisheries workers," and business operations related to "agricultural workers" are enacted for policies related to "agricultural workers." Note that in this embodiment, tag names can be set to any name that corresponds to the policy, measure, and business operations, and the scope of the invention is not limited by the name.

The granularity level may be set for tags that can be hierarchically classified. In other words, the granularity level may be a hierarchical classification other than policies, measures, sub-measures, and administrative projects.

The tag information can be set with tags related to the fiscal year, organization, business, budget, priority issues, achievements, etc. Furthermore, the tag information can be set with tags corresponding to classification conditions stored as master information. For example, the tag information can be set with various tags corresponding to search conditions for business information, such as an organization tag indicating the local government that executes the business, a geographic tag indicating the area of the local government, and a business tag indicating the classification of the business.

When registering or editing business information and/or business group information, the tag processing unit 23 selects the tag ID or tag name that corresponds to the business, and stores it in the memory unit DB in association with the business information.

The tag processing unit 23 can input text data such as the business name, business summary, business plan, affiliation name, and subsection name contained in the business information into the classification model, and output tag information as the classification result.

The classification model is a model that has been machine-learned using a dataset. The model may be a known model such as a neural network, logistic regression, decision tree, or k-nearest neighbor method. In this embodiment, a model suitable for natural language processing can be appropriately adopted. In this embodiment, since the tag information has a hierarchical structure, a hierarchical classification model is adopted.

The dataset used for machine learning of the model includes text data contained in the business information, and one or more tag IDs corresponding to the classification results of the business information. By machine learning the model using this dataset, a classification model is generated that outputs a tag ID as the classification result for any input of text data.

The memory unit DB may store a classification model that has been machine-learned by an external computer device or the like. The computer device acquires one or more data sets and executes machine learning processing of the model using the data sets. The computer device generates a trained classification model through the machine learning processing. The memory unit DB acquires and stores the generated classification model.

The storage unit DB may store multiple classification models. The classification models are machine-trained using, for example, text data according to the business type of the business and a data set including tag IDs. For example, a financial business classification model can be generated for the purpose of assigning a detailed financial business classification to business information related to a financial business. The tag processing unit 23 is configured to be able to select any classification model according to the rough business classification of the business to be input. This allows for more appropriate tag information to be assigned.

The tag processing unit 23 acquires text data included in the business information, inputs the text data into a classification model, and outputs a classification result. At this time, the tag processing unit 23 outputs one or more tag IDs as a classification result. The output one or more tag IDs are displayed on the display unit 905 of the user terminal 3 together with the likelihood. The tag processing unit 23 accepts a selection operation of one or more tag IDs via the user terminal 3, associates the tag IDs with the business information, and stores them in the storage unit DB. The tag processing unit 23 can automatically associate one or more tag IDs output as a classification result with the business information and store them in the storage unit DB. At this time, the tag processing unit 23 realizes automation of the association process by adopting a process of associating a tag ID with the highest likelihood with business information, or a process of associating a tag ID with a likelihood equal to or greater than a predetermined value with business information.

Figure 11 shows an example of the screen display of tag processing screens W6A and W6B displayed on the user terminal 3. In Figure 11 (a), the tag processing screen W6A includes a text input section W61, a tag display section W62, and a model selection section W63. The text input section W61 accepts the input operation of text data included in the business information. The tag display section W62 displays the tag name, etc. based on the tag ID already assigned to the business information. The model selection section W63 accepts the selection operation of a classification model to input the text data input to the text input section W61.

When a classification model is selected using the model selection unit W63 in FIG. 11(a), the screen is updated and displayed as the tag processing screen W6B as shown in FIG. 11(b). The tag processing screen W6B further includes a classification result display unit W64 and a details display unit W65. The tag processing unit 23 inputs the text data in the text input unit W61 into the selected classification model and obtains the tag ID output from the classification model.

The classification result display unit W64 displays the tag ID, which is the classification result, the tag name identified based on the tag ID, the granularity level, and the likelihood (score). The classification result display unit W64 assists the user in determining the tag ID by highlighting the tag ID with the highest likelihood and by sorting and displaying the tag IDs in order of likelihood. By accepting a selection operation for a tag ID, the classification result display unit W64 associates the tag ID with business information and completes the process.

The details display unit W65 displays details of the classification process using the classification model. The details include keywords extracted as features in the classification process and their degrees of association, the number of keywords and the number of characters contained in the text data, etc. By displaying details of the classification process, the details display unit W65 helps to prevent the classification process from becoming a black box. For example, by allowing the user to check whether any obviously inappropriate keywords are included in the classification process, this helps to support the user in determining the tag information to be ultimately assigned.

The tag information is used for evaluation based on an evaluation axis regarding the distribution of tag information. The evaluation unit 24 outputs an evaluation result based on the tag information. Specifically, the evaluation unit 24 outputs an evaluation result regarding the distribution of tag information assigned to the administrative and business information belonging to the business group information. The distribution status indicates the total number of each piece of tag information within the business group, etc. The distribution status indicates, for example, how many policies, measures, and businesses are associated with each other within the business group.

<Tag Information: Example 2>
A description will now be given of different examples of tag information in this embodiment. Fig. 12 shows a schematic diagram of tag information in this embodiment.

Figure 12 (a) shows an example of the data structure of tag information. According to Figure 12 (a), the tag information includes a tag ID, a tag name, a granularity level, and a related tag ID.

In this embodiment, the granularity levels are at least three hierarchies: policies, measures, and business operations. The granularity levels may also be four or more hierarchies including sub-businesses. The granularity levels can be defined as any number of hierarchies. The granularity levels correspond to policy tags, measure tags, and business operations tags, respectively. Note that the hierarchical division in this embodiment is an example, and the granularity levels can be defined as any number of hierarchies, and may be defined as a greater number of hierarchies or a smaller number of hierarchies. The granularity levels are not limited to the classification of policies, measures, business operations, and sub-businesses.

The related tag ID indicates a tag ID that specifies the relationship between the tag and other tags related in the hierarchical structure. The relationship may be any relationship such as a parent-child relationship, a sibling relationship, or a grandchild relationship, but it is preferable that the relationship is at least a form that allows specification of the parent-child relationship of adjacent hierarchies. The hierarchical structure is defined in the order of policy tag, measure tag, and business tag from top to bottom. For example, a measure tag is defined by associating the tag ID of one policy tag as a related tag ID, and a business tag is defined by associating the tag ID of one measure tag as a related tag ID. Note that a measure tag may be defined by associating the tag IDs of one or more business tags as related tag IDs, and a policy tag may be defined by associating the tag IDs of one or more measure tags as related tag IDs.

In this embodiment, the tag information includes basic tags with a defined granularity level, including policy tags, action tags, and business tags, and associated tags associated with the basic tags. The associated tags have a tag ID, a tag name, and a related tag ID that is a tag ID related to at least one of the basic tags. The associated tags may be configured to have the tag ID of the associated tag as the related tag ID.

Ancillary tags serve to add additional data to related basic tags. Ancillary tags are classified into cost tags, organization tags, fiscal year tags, performance tags, priority issue tags, etc. Ancillary tags are added when an administrative project includes additional data related to revenues and/or expenditures, such as individual expenses and specific financial resources. An organization tag is added when an administrative project includes additional data related to the implementing organization of a policy, measure, administrative project, etc. related to a basic tag. An implementing organization may indicate a department or section within an organization, or the organization itself, such as a local government. Ancillary tags are not limited to the above classifications, and are defined as various tags that are useful for referring to basic tags.

Figure 12 (b) shows an example of the hierarchical structure of the tag information shown in Figure 12 (a). According to Figure 12 (b), the tag information has a hierarchical structure in which policy tag A is the first hierarchical level, policy tags A and B that are children of policy tag A are the second hierarchical level, administrative and business tags A and B that are children of policy tag A are the third hierarchical level, and minor business tags A and B that are children of administrative and business tag A are the fourth hierarchical level. Here, minor business tag A is associated with associated tags A and B and is assigned associated data. In addition, associated tag A is associated with associated tag C and is assigned more detailed associated data. Note that the associated tag may be associated with any of policy tags, policy tags, administrative and business tags, and minor business tags.

In this embodiment, the storage unit DB stores information such as policy information, program information, and business/project information, which correspond to the hierarchy of tag information such as policy tags, program tags, and business/project tags.
As shown in Fig. 4A, the task/business information includes a task/business ID, task/business basic information including an overview of the task/business, and a tag ID for identifying tag information. The overview of the task/business includes, for example, the task/business name, the business overview, the execution year, the affiliation name, and the subdivision name.
The policy information has basic policy information including an outline of the policy, a tag ID for identifying tag information, etc., with a policy ID as a key. The outline of the policy includes the policy name, policy outline, execution year, department name, subsection name, etc.
The policy information has basic policy information including an outline of the policy, a tag ID for identifying tag information, etc., with a policy ID as a key. The outline of the policy includes the policy name, policy outline, implementation year, affiliation name, subsection name, etc.
The policy information, the program information, and the business/project information are associated with each other by the related tag IDs of the policy tag, the program tag, and the business/project tag, which are specified by the respective tag information. The policy information, the program information, and the business/project information may have associated policy IDs, program IDs, and business/project IDs. For example, the policy information may have associated program IDs, and the program information may have associated business/project IDs.

The policy information is configured to be capable of aggregating total budget amounts, total revenue amounts, etc. for policies based on the budget information of one or more associated administrative and business information. The policy information is configured to be capable of aggregating total budget amounts, total revenue amounts, etc. for policies based on the total budget amounts and total revenue amounts of one or more associated policy information.

In this embodiment, tag information related to a policy, measure, business project, or subproject is determined based on an overview of the policy, measure, business project, or subproject. The overview includes text data such as the business project name, project overview, execution year, department name, and subsection name of the business project information. The tag processing unit 23 outputs the classification result of the tag information based on the overview included in the policy, measure, business project, or subproject.

In this embodiment, the tag processing unit 23 inputs text data related to an outline of a policy, measure, or business operation into a classification model, and obtains the classification result from the classification model as an output. The classification model is stored in the storage unit DB. The classification model is a model that has been machine-learned using a dataset. In this embodiment, the model may be a neural network, a regression model, a decision tree, a k-nearest neighbor model, or the like.

The dataset used for machine learning of the classification model includes the following aspects:
In one embodiment, the data set includes text data on an outline of a policy, a program, or a business, and a classification result including at least a basic tag such as a policy tag, a program tag, a business tag, or a minor business tag. The classification result may include an additional tag.
In one embodiment, the data set includes text data on an outline of a policy, program, or business, and a classification result including one or more keywords corresponding to the basic tags. In this case, the basic tags and the corresponding keywords are stored in the storage unit DB as a correspondence table, and the basic tags corresponding to the keywords output as the classification result can be further output. The classification result may include one or more keywords corresponding to the associated tags. In this case, the correspondence table has the associated tags and the corresponding keywords, and the associated tags corresponding to the keywords output as the classification result can be output.

In this embodiment, the classification model has multiple classifiers. The classifiers output classification results for the input, and at least one classifier is provided for each hierarchy of tag information, and the output of the classification results is passed on to the classifier provided for the next hierarchy.

Figure 13 shows an example of the configuration of the classification model M in this embodiment. According to Figure 13, the classification model M includes a first classifier MA1 that receives input of text data related to an overview of a policy, measure, or business and outputs a classification result of a policy tag, a second classifier MB1, MB2 that receives input of the classification result of the first classifier MA and outputs a classification result of a policy tag, and a third classifier MC1, MC2 that receives input of the classification result of the second classifier MB and outputs a classification result of a business tag. The classification model M may further include a fourth classifier that receives input of the classification result of the third classifier MC and outputs a classification result of a minor business tag, and the classifiers can be configured according to the number of hierarchical levels.

The classification model M may be configured to include an associated tag classifier that accepts input of text data relating to an outline of a policy, measure, or business project, and outputs the classification results of the associated tags. The associated tag classifier may be configured to accept input of the classification results from the first to third classifiers, and output the classification results of the associated tags.

In this embodiment, the classifiers may be machine-trained using the above-mentioned datasets.

Each classifier outputs multiple tag information and their likelihoods as classification results. The likelihoods are indexes or estimates that indicate the degree of probability that the tag information output as a classification result is the one.

In the classifier according to the present embodiment, a threshold is set for the likelihood distribution, which is a distribution of the likelihood of each of a plurality of pieces of tag information, and is classified into, for example, the following patterns.
Pattern 1: The likelihood of a particular tag is high compared to the likelihood of other tags.
Pattern 2: The likelihood of each tag is relatively equal.

Pattern 1 is identified by setting a threshold value for the difference between the likelihood of a specific tag and the likelihood of other tags. Note that there may be multiple specific tags.
Pattern 2 is identified by setting a threshold value for the difference in likelihood of a plurality of tags. Note that, in pattern 2, a predetermined number of tags may be set, and a threshold value may be set for the difference in likelihood of the tags of the predetermined number of tags.

The classifier identifies at least one of the above patterns based on a threshold set in the likelihood distribution, and decides whether to input the classification result to a lower classifier. For example, if the pattern is 1, the classifier inputs the classification result to the lower classifier, and if the pattern is 2, the classifier does not input the classification result to the lower classifier. In the case of pattern 2, the classification model M outputs a classification result including tag information corresponding to the classifier to which the classification result was last input. This makes it possible to output, as the classification result, tags that are highly likely to be tag information in a higher hierarchy, such as policy tags or action tags.

The flow of outputting the classification results of the business/business tag will be described with reference to FIG.
The first classifier MA1 accepts input of text data of the business summary of the administrative and business information, and outputs a classification result including policy tag B1 and likelihood 0.95 to classifier MB1, and a classification result including policy tag B2 and likelihood 0.05 to classifier MB2.
The classifier MB1 receives an input of the classification results, and outputs the classification results including the policy tag C1 and the likelihood of 0.75 to the classifier MC1, and the classification results including the policy tag C2 and the likelihood of 0.25 to the classifier MC2.
The classifier MC1 receives an input of the classification results, and outputs a classification result including the business/office tag A and a likelihood of 0.88, and a classification result including the business/office tag B and a likelihood of 0.12.
The classifier MC2 receives an input of the classification results, and outputs a classification result including the business/task tag C and a likelihood of 0.58, and a classification result including the business/task tag D and a likelihood of 0.42.
Here, for example, a threshold value of 0.5 for the likelihood distribution is set for classifiers MC1 and MC2, and classifier MC1 identifies the likelihood distribution as pattern 1 and outputs the business/task tag A and the business/task tag B as the classification result. Classifier MC2 identifies the likelihood distribution as pattern 2 and outputs the policy tag C2 as the classification result.
The classification model M outputs, as classification results, the business/business tag A, the business/business tag B, and the policy tag C2, and their respective likelihoods. The likelihoods are derived by calculating the likelihoods output from the first to third classifiers that have passed through. The likelihoods are calculated, for example, by multiplication, and the likelihood of the business/business tag A is 0.95*0.75*0.88=0.627, the likelihood of the business/business tag B is 0.95*0.75*0.12≒0.086, and the likelihood of the policy tag C2 is 0.95*0.25≒0.238.
These classification results are displayed as tag names and scores in the classification result display section W64 of the tag processing screen W6B in FIG. 11(b).

An example of the implementation of the display on the tag processing screen W6B in Fig. 11(b) will be described. The classification result display section W64 displays tag names in descending order of likelihood based on the likelihood, which is the classification result by the classification model M.
In one aspect, the displayed tag name may include an administrative/business tag A that is finally output via classifier MA1, classifier MB1, and classifier MC1, and may further include a policy tag B1 corresponding to the classifier MA1 that has been passed through, and a measure tag C1 corresponding to the classifier MB1.
In one embodiment, when the tag name displayed includes the business tag A that is finally output via classifiers MA1, MB1, and MC1, it may be only the final output business tag A. Even if the likelihood of the business tag A is smaller than the likelihood of the policy tag B1 or the measure tag C1, if the likelihood distribution is pattern 1, it is highly likely to be the tag name output by a lower-level classifier. This makes it possible to more efficiently select and decide on tag names.

The classification model M can also classify the associated tags using a similar procedure. For example, the classification model M outputs the classification results of the associated tags by inputting the classification results from each classifier to a classifier for the associated tags. In addition, the associated tags may be classified using different classification models for classifying the associated tags.

The basic tags and additional tags are assigned as centrally defined tags to policies, programs, and administrative projects, with the aim of improving the searchability, identifiability, and ease of management of such information.

When the search processing unit 26 receives a designation operation of tag information via the user terminal 3, it refers to the granularity level of the tag information and acquires business information associated with at least the tag information of that granularity level. In addition, when the search processing unit 26 receives a designation operation of tag information, it refers to the granularity level of the tag information and acquires business information associated with the tag information of that granularity level and tag information belonging to a lower hierarchy of that granularity level.

More specifically, the search processing unit 26 accepts at least a basic tag specification operation, and acquires administrative and business information so as to include administrative and business information associated with tag information that has the same basic tag but does not have the same organizational tag. Here, the organizational tag includes tags of executive organizations such as different local governments, and the search processing unit 26 can search for information including administrative and business information that has been assigned organizational tags of different local governments. This allows information on policies, measures, and administrative and business activities, which previously did not have uniform names or classifications for each local government, to be managed as similar tag information, making it possible to support the use of information and collaboration with other local governments.

<Business search>
As described above, the business information is associated with business group information and/or tag information, thereby contributing to improving the searchability of the business information. The search processing unit 26 can accept input of search conditions including classification conditions for identifying business group information and tag names for identifying tag information via the user terminal 3, search for corresponding business information and business group information based on the search conditions, and output the results to the user terminal 3.

Here, the search conditions may be not only for the administrative business information of the local government to which the user terminal 3 belongs, but also for administrative business information outside the local government to which the user terminal 3 belongs. Specifically, the search processing unit 26 searches for administrative business information with different organizational tags and common search conditions including the business tag, thereby obtaining administrative business information of the business classification to be referred to in other local governments. Conventionally, the definition of the classification of policies, measures, and administrative business was not uniform, but was arbitrarily set for each local government, each department, each person in charge, etc., but by managing administrative business information according to a unified administrative business definition such as business group and tag information, it becomes easier to obtain information such as the performance related to administrative business outside the local government. For example, financial personnel, original department personnel, and general affairs managers can plan, organize, execute, and evaluate new businesses while referring to the budget composition of other local governments.

It is preferable that the business information is associated with at least one piece of tag information. The group registration unit 22 may use the tag information when setting the classification conditions (particularly, business classification) of the business group information.

The search function for business information may also be provided to the terminal devices of local residents. This will help provide highly transparent business information to local residents, etc.

The following describes a specific example of the administrative business management system 1.

＜Planning stage＞
In the planning stage, the user terminal 3 of the original section staff creates planning information in response to the plan creation request and transmits a planning request to the administrative business management device 2. The update unit 25 of the administrative business management device 2 acquires the planning request and updates the progress status of the planning stage associated with the target administrative business information from before request to requested. When the update unit 25 acquires an approval instruction for the planning information corresponding to the submitted planning request via the user terminal 3 of the manager, it updates the progress status from requested to assessed. When the update unit 25 acquires a non-approval instruction for the planning information, it updates the progress status from requested to before request. When the progress status becomes assessed, the progress in the planning stage is completed. When the progress in the planning stage is completed, the update unit 25 may automatically update the progress status to the budget preparation stage. When the planning stage becomes assessed, the administrative business management device 2 transmits a notification to the user terminal 3 of the financial staff. The financial staff determines the budget preparation policy while referring to the assessed planning information.

The administrative business management device 2 may accept an operation to assign a priority to assessed business information via the administrator's user terminal 3, and store the operation in the memory unit DB in association with the business information.

<Budget preparation>
At the budget preparation stage, the user terminal 3 of the original section staff creates budget information in response to a request from the financial staff to create a budget request document, and transmits the budget request to the administrative business management device 2. The update unit 25 of the administrative business management device 2 acquires the budget request, and updates the progress status associated with the target administrative business information from "pre-requested" to "requested." When the update unit 25 acquires an approval instruction for the budget information corresponding to the submitted budget request via the financial staff's user terminal 3, it updates the progress status from "requested" to "assessed." Note that when the update unit 25 acquires an instruction to not approve the budget information, it updates the progress status from "requested" to "pre-requested." When the progress status becomes "assessed," progress at the budget preparation stage is completed. The update unit 25 may automatically update the progress status to the execution stage.

When the administrative project management device 2 receives an instruction to approve or disapprove a budget request, it can provide the priority associated with each task and project information to the user terminal 3 of the approver (financial officer, manager). This allows the approver to, for example, evaluate tasks and projects in order of priority while referring to the priority order.

<Execution>
In the execution stage, the user terminal 3 of the original section staff member transmits an execution start request to the administrative business management device 2 in conjunction with the execution of the business. The update unit 25 acquires the execution start request and updates the progress status associated with the target business information during execution. In addition, the user terminal 3 of the original section staff member may transmit an execution information record request such as the amount of execution and execution results to the administrative business management device 2 in conjunction with the execution of the business, and store it in the storage unit DB in association with the business information as an execution history. The update unit 25 acquires a request to complete the execution of the business via the user terminal 3 of the original section staff member, or when the deadline for the execution of the business has passed, updates the progress status to "executed." When the progress status becomes "executed," the progress in the execution stage is completed. The update unit 25 may automatically update the progress status to the execution stage.

<Administrative evaluation>
In the evaluation stage, the user terminal 3 of the original section staff member transmits a request to register evaluation information for the executed task/business information to the administrative task management device 2. The update unit 25 acquires the evaluation request and updates the progress status associated with the target task/business information to "evaluated." When the progress status becomes "evaluated," all progress in the target execution year is completed.

In this embodiment, in the execution stage or administrative evaluation stage, the administrative business management device 2 can accept input regarding the results in the business information. The administrative business management device 2 accepts input as a result value for the quantitative evaluation results corresponding to the quantitative evaluation items. The administrative business management device 2 accepts input for the task evaluation results corresponding to the task evaluation items by updating the status of completed tasks to completed.

<Evaluation Department>
In this embodiment, the evaluation unit 24 can output evaluation results of various objects according to the evaluation axis. The evaluation axis indicates an axis that specifies the object to be evaluated. The evaluation unit 24 can output evaluation results based on the evaluation axis corresponding to the requested object to the user terminal 3 by accepting a request for a specific evaluation result via the user terminal 3.

The evaluation unit 24 outputs the evaluation results of the administrative business based on the evaluation axis associated with the business group information. The evaluation unit 24 also outputs the evaluation results for each business group based on the evaluation axis associated with the business group information.

In this embodiment, the evaluation axes include progress, progress, achievement, and distribution. The evaluation unit 24 outputs evaluation results regarding the progress, progress, achievement, and distribution based on these evaluation axes.

The progress evaluation axis is used to evaluate the progress status for each stage of progress status. The evaluation unit 24 outputs an evaluation result regarding the progress status in the business group based on the progress status of the business and project information associated with the business group information. Specifically, based on the total number of business and project information belonging to the business group information and the quantity of business and project information having a specified progress status, the evaluation result regarding the progress status is output as a percentage or total number by progress status for the entire business group. The evaluation result is output based on the progress status according to each category of the planning stage, budget preparation stage, execution stage, and administrative evaluation stage.

The evaluation axis of the progress is used to evaluate the progress regarding fluctuations in budget information. The evaluation unit 24 calculates the total budget amount and the total revenue amount by fiscal year based on the budget information of the administrative projects belonging to the business group. The evaluation unit 24 outputs the progress of the total budget amount and/or the total revenue amount by fiscal year in the business group. The progress is shown by the amount of increase/decrease from a specified fiscal year, the rate of increase/decrease, or a graph showing the trend of the total budget amount and/or the total revenue amount by fiscal year.

The achievement status evaluation axis is used to evaluate the achievement status of goals set in quantitative evaluation items and task evaluation items. The evaluation unit 24 evaluates the achievement status of the business and administrative information based on the actual results entered as quantitative evaluation results against target values such as KPIs and KGIs set in the quantitative evaluation items. Here, the achievement status of individual business and administrative information indicates whether the actual results exceeded the target values, the achievement rate of the actual results against the target values, etc.

The evaluation unit 24 evaluates the progress of the business information based on the task completion status input as the task evaluation performance for the task set in the task evaluation item. Here, the progress of individual business information indicates whether the task was completed, whether the task was completed within the schedule, the progress rate for multiple tasks, etc. The evaluation unit 24 may evaluate the progress of each of the normal tasks and important tasks.

The evaluation unit 24 evaluates the achievement status of the goals of the entire business group based on the achievement status of the individual business and project information associated with the business group information. Here, the achievement status of the business group indicates the average achievement rate of the business and project, the total number of goals achieved and the achievement rate, the total number of normal tasks and priority tasks achieved and the achievement rate, etc.

The achievement status may indicate the progress of the goal achievement status. In this case, the achievement status is output in the form of a graph, table, or map showing, for example, the increase or decrease in the achievement rate of the goal from a specified fiscal year or the increase or decrease in the number of achievements.

The evaluation axis of the distribution situation is used to evaluate the distribution situation of the tag information. The evaluation unit 24 counts up each tag ID assigned to the administrative business belonging to the business group. The evaluation unit 24 outputs the quantity of each tag ID based on the counted tag IDs as the evaluation result regarding the distribution situation. Here, the evaluation result regarding the distribution situation may be output in a graph format or the like, showing the quantity for each tag ID.

The evaluation unit 24 can output evaluation results by policy, measure, or business project, depending on the granularity level of the policies, measures, and business projects in the tag information. Here, the evaluation unit 24 outputs the evaluation results using the evaluation axes of progress, progress, achievement, and distribution. For example, the evaluation unit 24 can output, as evaluation results, comparisons of progress by measure, and comparisons of goal achievement by measure. When evaluating progress by measure, the evaluation results of progress are output based on the progress status of the business projects that belong to the measure.

The evaluation unit 24 can output evaluation results in a comparable manner by policy unit, measure unit, sub-measure unit, administrative business unit, or business group unit.

Figure 14 shows an example of the comparative evaluation screen W7 displayed on the user terminal 3. The comparative evaluation screen W7 displays comparative evaluation results for policy units, policy units, sub-policy units, administrative business units, or business group units.

The comparative evaluation screen W7 comprises a first display section W71, a second display section W72, a third display section W73, a fourth display section W74, and an add button W75. The first display section W71 to the fourth display section W74 each display evaluation results and administrative tasks that are arbitrarily set via the user terminal 3. When the add button W75 is pressed, it accepts setting operations such as the content to be displayed in the fifth display section and the display format, and generates the fifth display section based on the setting operations. The comparative evaluation screen W7 shows an example of the display of four display sections, the first display section W71 to the fourth display section W74, but the number of display sections is not limited and they can be added, edited, or deleted.

In Fig. 14, the first display unit W71 displays a list of KGI evaluation results for each business group. Here, the average or aggregate value of the KPI performance values of each task business belonging to the business group is calculated as the KGI performance value for the business group and displayed as the KGI evaluation result. The first display unit W71 is referred to by the user when selecting a task business or business group to be continued, discontinued, or the budget increased or reduced.
In FIG. 14, the second display section W72 displays an overview of one or more favorite business operations.
In FIG. 14, the third display section W73 displays the number of tasks and projects at the budget preparation stage in a graph format by progress status.
14, the fourth display unit W74 displays the percentage of tasks and projects that belong to a business group and have a certain or higher progress status (e.g., assessed) at the budget preparation stage as a list of evaluation results for each business group. The fourth display unit W74 can display the business groups in a distinguishable manner by highlighting or coloring them according to the percentage. The fourth display unit W74 is provided as an interface that allows the user to grasp at a glance which business groups have poor progress statuses.

<Priority Issues>
In this embodiment, the administrative project management device 2 accepts an instruction to register priority issue information via the user terminal 3, and stores it in the storage unit DB. The priority issue information is information for managing priority issues in a target year, and includes a priority issue ID, a priority issue name, a priority issue summary, priority projects such as policies, measures, sub-measures, and administrative projects for solving the priority issues, and organizations responsible for the execution of the priority projects. Multiple policies, measures, sub-measures, and administrative projects may be set for the priority projects.

The priority issue information is associated with the task and project ID of the task and project registered as a priority project. Task and project information registered as a priority project is assigned tag information indicating that it is a priority issue. The priority issue information has a total priority issue budget and a total priority issue revenue based on the budget information of the task and project information belonging to the priority project. The total priority issue budget indicates the total budget amount of each task and project. The total priority issue revenue indicates the total revenue amount of general financial resources of each task and project. When setting the budget limit amount, the priority issue information can use financial resources classified as the priority budget. In this way, the method of setting the budget limit amount is different for general projects and priority projects, and budgets can be compiled using financial resources that can be set for each.

<Matching function>
There are cases where administrative tasks and business are executed by the government, and cases where the government outsources or requests collaboration with a private company, etc., and the requested company executes the task. The government business management system 1 provides a platform that supports matching between the government and the requesting company when outsourcing or collaborating on administrative tasks and business. In this embodiment, the requesting company includes private companies and administrative agencies such as other local governments.

The administrative business management system 1 further includes a requested terminal 4. The requested terminal 4 is a terminal device operated by a person in charge of a private company or the like. The requested terminal 4 may be a smartphone, personal computer, tablet terminal, or the like having the same hardware configuration as the user terminal 3. The requested terminal 4 is connected to the communication network NW and is configured to be capable of data communication with the administrative business management device 2 and the like.

The matching processing unit 27 accepts the input operation of the public recruitment information for the business, including the organizational classification and the business classification, via the user terminal 3, and stores it in the memory unit DB. The matching processing unit 27 may accept the selection operation of the business information via the user terminal 3, and generate it based on the business information. The matching processing unit 27 accepts the input operation of the application information for the business, including the organizational classification and the business classification, via the request destination terminal 4, and stores it in the memory unit DB.

The organization classification includes a classification for distinguishing between a public offering organization, which indicates that the public offering organization is an administrative agency such as a local government making a public offering, and an applicant organization, which indicates that the private company or administrative agency making an application. The business classification includes a classification for distinguishing between the classification of the business for which the public offering organization is making an offering, the classification of the business in which the private company making an application specializes, and the classification of the business in which the administrative agency making an application wishes to collaborate. The business classification may use the tag name of the tag information, etc.

The matching processing unit 27 accepts an input operation to authorize the application information for the public recruitment information via the user terminal 3 of the recruiting organization, thereby establishing a match for the outsourcing or collaboration of the administrative business corresponding to the public recruitment information and the application information. The matching processing unit 27 also accepts an input operation to authorize the public recruitment information for the application information via the requestee terminal 4 of the applicant organization, thereby establishing a match for the outsourcing or collaboration of the administrative business corresponding to the public recruitment information and the application information.

FIG. 15 shows an example of the screen display of the matching screen W8 displayed on the user terminal 3 or the request destination terminal 4. In FIG. 15, the matching screen W8 displays a list of public solicitations for business operations based on the public solicitation information. The matching screen W8 includes a classification switching section W81 and a business display section W82. The classification switching section W81 accepts a selection operation related to the public solicitation information, application information, and proposal information, and switches the information displayed as a list in the business display section W82. The business display sections W82A to 82C display the name, organization classification, summary, publication end date, business classification, and matching status of the target business operations based on the public solicitation information, application information, or proposal information. In FIG. 15, the business display section W82 displays the public solicitation organization such as a local government that will carry out the public solicitation as the organization classification. In addition, the business classification is displayed based on tag information associated with the target business operations information. The matching status indicates the number of application information for the target public solicitation information, the number of proposal information for the public solicitation information, etc.

When an input operation is received to allow application information for the public recruitment information, the proposal information is generated by receiving the input operation via the request destination terminal 4 of the applicant organization, and includes a proposal outline such as a specific response plan for the publicly recruited business. The matching processing unit 27 further receives an input operation to allow proposal information for the public recruitment information via the user terminal 3 of the public recruitment organization, thereby establishing a match between the public recruitment organization and the applicant organization as a formal request. Note that an upper limit is set for the number of application information and proposal information for the public recruitment information, and the matching processing unit 27 can only execute matching processing within the upper limit.

<Administrative business management device: Implementation example 2>
Hereinafter, a second implementation example of the administrative project management device 2 will be described. Fig. 16 shows a block diagram of the administrative project management device 2 in this embodiment. Note that the same components as those in the first implementation example are denoted by the same reference numerals and will not be described.

There are systems of administrative projects, such as policies, measures, minor measures, administrative projects, and minor projects. In this embodiment, these are collectively defined as the policy system. In other words, policy system information includes policy information, measure information, minor measure information, administrative project information, and minor project information. In the following explanation, when the policy system is used, no distinction is made between the policies, measures, etc. mentioned above. These policy systems correspond to the granularity levels mentioned above.

The project registration unit 21 accepts registrations of policy system information related to policies, measures, sub-measures, administrative projects, and sub-projects enacted based on government ordinances, and stores it in the memory unit DB. Here, the policy information, measure information, sub-measure information, administrative project information, and sub-project information contained in the policy system information are assumed to have the same data structure as in implementation example 1. For simplicity, the following explanation uses administrative project information as an example, but other policy system information may also be used.

According to FIG. 16, the administrative business management device 2 is connected to the user terminal 3 so as to be capable of data communication. Furthermore, the administrative business management device 2 and the memory unit DB are configured so as to be capable of data communication. The memory unit DB is provided inside or outside the administrative business management device 2. In implementation example 2, an administrative business management system 1 is implemented that includes at least the administrative business management device 2, the user terminal 3, and the memory unit DB.

The administrative business management device 2 has, as its functional configuration, a business registration unit 21, an action history recording unit 28, an action history acquisition unit 29, and an action status output unit 30. The business registration unit 21 accepts an instruction to register administrative business information via the user terminal 3, and stores it in the memory unit DB. The action history recording unit 28 acquires the action history executed via the user terminal 3, and stores it in the memory unit DB. The action history acquisition unit 29 accepts a request for output of the action status via the user terminal 3, and acquires the action history necessary for output of the action status from the memory unit DB. The action status output unit 30 outputs the action status based on the action history acquired by the action history acquisition unit 29.

The user terminal 3 can register administrative and business information by sending an instruction to register the administrative and business information to the administrative and business management device 2. The user terminal 3 can record an action history related to actions performed on the registered administrative and business information by sending the administrative and business management device 2. The user terminal 3 can send an instruction to output an action status to the administrative and business management device 2, and receive from the administrative and business management device 2 the output result of the action status for the administrative and business information. The user terminal 3 displays the received output result on the display unit, allowing the user to grasp the action status for the administrative and business.

The user terminal 3 can transmit an instruction to register policy system information to the administrative business management device 2 and register the policy system information. The user terminal 3 can transmit an action history regarding actions related to the policy system information to the administrative business management device 2 and record the action history. The user terminal 3 can transmit an instruction to output the action status to the administrative business management device 2 and obtain the output results of the action status related to the policy system information from the administrative business management device 2. The user terminal 3 can grasp the action status related to the policy system by displaying the obtained output results on the display unit.

In this embodiment, there are multiple user terminals 3. Furthermore, the user terminals 3 are set with different authority settings depending on the department and position within the owner's organization. Specifically, authority settings are set by department, such as the original department/original section manager, general affairs manager, and finance manager. Furthermore, authority settings are set by position, such as department manager, section manager, and general. For example, certain actions, such as approval actions described below, are permitted only to be performed by user terminals 3 with authority settings, such as department managers and section managers.

In this embodiment, the administrative business management system 1 manages the history of actions related to the policy system and outputs the status of actions related to the policy system. Here, actions related to the policy system include answering questions and raising issues in administrative work. Answering questions refers to answers given in a specified assembly or regular meeting, and refers to administrative work such as question and answer sessions. Raising issues refers to administrative work that raises issues discovered through administrative work such as answering questions or executing projects.

The behavioral history related to policy system information includes behavioral history associated with policy system information, or behavioral history associated with actions related to policy system information (such as responses and raising issues). The behavioral status related to the policy system includes behavioral status regarding policies, measures, and business projects, or behavioral status associated with actions related to policies, measures, and business projects (such as responses and raising issues). In other words, the behavioral history includes behavioral history associated with response information and priority issue information, and the behavioral status includes behavioral status regarding responses and raising issues.

In this embodiment, the administrative business management device 2 accepts an instruction to register reply information and priority issue information via the user terminal 3, and stores the reply information and priority issue information in the memory unit DB.

In one aspect, the reply information includes at least a reply ID, a reply name, a question summary, and a reply summary. Based on the reply information, the administrative business management device 2 can generate and register priority issue information regarding the priority issue raised in the reply. The generated priority issue information is registered in association with the reply information. The reply information is generated by registering the question summary, and the reply summary can be further registered as a response to the question summary.

In one embodiment, the priority issue information includes at least a priority issue ID, a priority issue name, and a priority issue summary. Based on the priority issue information, the business registration unit 21 can generate and register information related to policies, measures, sub-measures, and administrative projects to solve the priority issue. The generated administrative and administrative information is registered in association with the priority issue information.

<Data structure of behavior history>
In this embodiment, the storage unit DB includes a behavior history storage unit that stores information related to the behavior history. Fig. 17 illustrates an example of the data configuration of the information related to the behavior history.

As shown in FIG. 17(a), the action history is stored by associating the action history ID with the task/business ID. The action history has a task/business ID, an action history ID, an actor ID for identifying the user who performed the action, and a type of action history. In this embodiment, the types of action history include pointing out actions, commenting actions, approval actions, execution actions, budget preparation actions, etc. Note that the types of action history are not limited to these, as long as they relate to actions on a task/business.

In this embodiment, the pointing out action, the comment action, and the approval action have posting data in a chat format or the like posted via the user terminal 3, as shown in FIG. 17(b). The pointing out action, the comment action, and the approval action have an action history ID, an actor ID, a type of action history, a pointing out element, posting data, a posting date and time, etc. The posting data is generated by the actor's optional input, such as text data or an attachment.

The pointed out element points out unclear points or points that need to be corrected with respect to a business operation or the actions of a user (actor) with respect to the business operation. In addition to the pointed out element, the pointed out action may further include a deadline for a response such as a reply or correction, and a person in charge of responding by replying or correcting the action. The pointed out action is a behavioral history that serves as the starting point when it is output as the action status with respect to the business operation.

A comment action is a comment made about a task or a user's action on a task. A comment action can be associated with a pointing out action or other comment action, and a series of related comments are displayed in thread format. A comment action is a history of actions that serves as the starting point and/or ending point when output as the action status for a task.

An approval action is an approval for a task or a user's action on a task or a business. Approval actions are generated, for example, by approval of planning information for task or business information, approval of budget information, approval of evaluation information, etc. Approval actions are controlled so that they can be executed by approval operations permitted for a specific user terminal 3 that has approval authority in an organization. Approval actions can be associated with pointing out actions and comment actions, and may be able to respond to points pointed out or approve proposals raised in comments. Approval actions can also be associated with budget preparation actions, which will be described later, and may include approval for budget preparation and budget amendments. Approval actions are action history that are the end point when output as the action status for a task or business.

As shown in FIG. 17(c), an execution action includes an action history ID, an actor ID, a type of action history, a report name related to the execution, report contents, and a report date. An execution action is generated by inputting the status of the execution of a task or business in a timely manner via the user terminal 3 during the execution stage of the task or business.

The budget compilation action is generated by receiving a budget compilation instruction to compile a budget or a budget correction instruction to correct a budget via the user terminal 3. The budget compilation action associated with a budget compilation instruction is generated so as to be able to distinguish between priority budgets for priority business projects and general budgets for general business projects. The budget compilation action associated with a budget correction instruction is generated as a behavioral history regarding the decision to correct the budget when an execution problem arises during the execution stage of a business project.

As shown in FIG. 17(d), the budget compilation action accompanying the budget correction instruction includes an action history ID, an action performer ID, a type of action history, a report name related to the budget correction decision, the report content, the report date, a related action ID that identifies the related action history that led to the decision, a priority flag indicating the need for priority measures, a type of supplementary budget, and factors. The related action ID refers to action history related to the budget correction decision, such as the action history ID of the execution action. The type of supplementary budget indicates whether there is no supplementary budget, or if there is a supplementary budget, the timing (May supplementary budget, June supplementary budget, etc.). The factors indicate the type of factor, such as whether the execution problem is due to external or internal factors.

In this embodiment, the business information is classified at least into business types: general business and priority business. Priority business is a business planned to solve a priority issue in the administration, and is allocated a priority budget in addition to the general budget. In addition, priority business is given priority over general business in budget allocation, not limited to the priority budget.

Figure 17 (e) shows an example of the data structure of the action history of priority business projects and general business projects. Priority business projects and general business projects are distinguished by business type, and the specified actions of general business projects are controlled based on the specified action history of priority business projects.

In this embodiment, the type of behavior history includes answering behavior. The answering behavior includes a behavior history ID, an actor ID, a type of behavior history, an answer summary, and an answering date. The answering behavior is generated by making an answer via the user terminal 3 and inputting the situation at the appropriate time. The answering behavior is stored by associating the answer ID with the behavior history ID of the answering behavior.

In this embodiment, the type of behavior history includes a raised action. A raised action includes raising an issue based on a response or execution factor, and raising a policy system that includes administrative projects based on the issue.

In this embodiment, the type of the action history includes an issue-raising action. The issue-raising action includes an action history ID, an actor ID, an action history type, issue content, a date of raising the issue, and a priority issue ID of the priority issue raised. The issue-raising action may further include issue factors that led to the issue being raised. The issue factors include answer factors and execution factors. The answer factors are attached to the issue discovered through the answer, and the factors are identified by the answer ID that identifies the answer or the action history ID of the answer action. The execution factors are attached to the issue discovered through execution, and the factors are identified by the business ID that identifies the business information that is the subject of the execution or the action history ID of the execution action. The execution factors may be identified by the execution action having a priority flag.

In this embodiment, the type of action history includes a policy system proposal action. The policy system proposal action includes an action history ID, an actor ID, a type of action history, an overview of the policy system, a proposal date, and an ID of the proposed policy system (such as an administrative business ID). The policy system proposal action can further include a target issue that led to the proposal of the policy system. Target issues include priority issues identified by a priority issue ID, etc.

As mentioned above, policy system information such as business and project information is linked to the priority issue information that was the basis for the proposal of the business or project, and the priority issue information is linked to the response information and business and project information that were the basis for the priority issue. This makes it possible to manage and understand the series of events that led to the proposal of the business or project.

In this embodiment, the behavioral history may be configured to be associated with business information and further associated with business group information to which the business information belongs. The behavioral history may also be configured to be associated with business group information. In the following explanation, the former is used as an example, but the present invention is not limited to this embodiment, and the latter embodiment may also be adopted.

<System processing sequence>
FIG. 18 illustrates a processing sequence performed among the administrative project management device 2, the user terminal 3, and the storage unit DB.

First, the user terminal 3 transmits the task and business information input by the user to the administrative business management device 2 (S31). The administrative business management device 2 stores the received task and business information in the memory DB (S32). The user terminal 3 transmits the action history for the task and business performed by the user to the administrative business management device 2 (S33). The administrative business management device 2 stores the received action history in the memory DB (S34). The user terminal 3 transmits an action status request for outputting the action status for the task and business to the administrative business management device 2 (S35). The administrative business management device 2 outputs an action history request to the memory DB to acquire the action history required to output the action status in response to the action status request (S36). The memory DB passes the requested action history to the administrative business management device 2 (S37). The administrative business management device 2 outputs the action status for the task and business to the user terminal 3 based on the acquired action history (S38).

In S31 and S32, the business information may be response information or priority issue information. In S33 and S34, the behavior history may be behavior history related to policy system information. In S35, the behavior status request may be a request for output of behavior status related to the policy system. In S37, the output behavior status may be behavior status related to the policy system.

<Processing flow chart of the device>
Fig. 19 illustrates a processing flowchart relating to an action history and an action status based on the action history by the administrative project management device 2. Note that the following description of Fig. 19 is not limited to the processing of an action history for an administrative project and an action status for an administrative project.

Step S41: The business registration unit 21 accepts a registration request for business information entered via the user terminal 3 and stores it in the memory unit DB.

Step S42: The action history recording unit 28 acquires the action history for the business information input through the user terminal 3, associates it with the business information, and stores it in the memory unit DB.

Step S43: The behavior history acquisition unit 29 accepts a behavior status request for outputting the behavior status for an administrative task that was input via the user terminal 3.

Step S44: The behavior history acquisition unit 29 outputs a behavior history request to the memory unit DB to acquire the behavior history required to output the behavior status requested by the behavior status request.

Step S45: The behavior history acquisition unit 29 acquires the behavior history from the memory unit DB in response to the behavior history request.

Step S46: The behavioral status output unit 30 outputs the behavioral status for the business based on the acquired behavioral history.

<Screen display>
20A shows an example of a screen display of a suggested action list W200 regarding suggested actions for an administrative project. The suggested action list W200 is displayed on the display unit 905 of the user terminal 3. In the illustrated example, the suggested action list W200 is displayed as a menu of the project display unit W44 in FIGS. 7 and 8.

The pointed out action list W200 displays a list of pointed out actions W201A, W201B for business operations. The pointed out actions displayed in the list can be sorted by response deadline, urgency, status, creation date and time, etc., and can also be searched by keywords, categories, tags, etc. of business information. When the user presses the Add button W202, it transitions to the pointed out action registration screen W210 shown in FIG. 20(b). The pointed out action W201 can be associated with a comment action by accepting the input of posted data by comment.

The pointed out action registration screen W210 includes a pointed out action input section W211, a register button W212, and the like. The pointed out action input section W211 accepts the registration operation of a pointed out action for an administrative project via the user terminal 3. The pointed out action includes the title of the pointed out element, the pointed out element, the person in charge of handling, the deadline for handling, and the posted data in the form of a comment. The pointed out element is input by selecting the administrative project to be pointed out, and further selecting the element in the administrative project to be pointed out. When the register button W212 is pressed, the action history related to the pointed out action is sent to the administrative project management device 2.

Figures 21(a) to (c) show examples of displaying chat-style posts of pointing out actions, commenting actions, and approving actions, respectively. Figures 21(d) and (e) show examples of screen displays of chat screens W330 and W340 that display action history in chat format.

The posting W300 of a pointed out behavior displays information about the person who has done the behavior, including the icon, name, and affiliation of the person who has done the behavior, the posting date and time, and the pointed out behavior. The posting W300 can also accept comments and other behaviors as replies.

The comment behavior posting W310 displays the actor information, including the actor's icon, name, affiliation, etc., the posting date and time, and the comment behavior. The posting W310 can accept comment behavior as a reply and approval behavior based on a comment.

The approval action post W320 displays the actor information, including the actor's icon, name, affiliation, etc., the posting date and time, and the approval action. The post W320 includes an indication of the type of approval, such as the approver's job title (finance manager, finance department manager, etc.) and the approval stage (first approval, second approval, etc.). In this embodiment, the approval action post W320 is displayed in a different color and layout design so that it can be distinguished at a glance from other posts. Note that the approval action post may also include posting data such as comments.

Chat screen W330 is a display example including a comment posted W331 by a finance department staff member (AAA), a comment posted W332 by the finance department manager (BBB), and an approval posted W333 by the finance department manager (BBB). Chat screen W330 displays in chat format the process in which the finance department staff member and the manager exchange comments to confirm the budget document, and the manager approves it.

Chat screen W340 is a display example including a posting W341 of a criticism made by the finance section chief (BBB), a posting W342 of a comment made by the finance section staff member (AAA), a posting W343 of a first approval action made by the finance section chief (BBB), and a posting W344 of a second approval action made by the finance section chief (CCC). Note that as indicated by "12 replies," posting W342 is associated with the posting of comment actions made by multiple users. Chat screen W340 displays in chat format the process in which the finance section staff member, who received criticism from the finance section chief, communicates with multiple users through comments, and the finance section chief and staff member each give two-stage approval after receiving the results.

Note that, while chat screens W330 and W340 show an example of posting an approval action in association with a comment action and/or a pointing out action, the comment action and pointing out action can be omitted by posting an approval action in association with the planning information, budget information, evaluation information, etc. of the business information.

Figure 22 is an example of the chart screen W400 that displays a time series chart output based on behavioral history.

The chart screen W400 displays a behavioral status in which the icon of the actor is shown in a time series chart W410 based on a behavior history including at least one selected from among a pointing out behavior, a commenting behavior, and an approval behavior, and information indicating the actor who performed the behavior history. The information indicating the actor is an actor ID, etc., and the name, icon, etc. are referenced based on the actor information identified by the actor ID.

The time series chart has action icons W421 to W427 (hereinafter collectively referred to as action icons W420) and actor icons W431 to W438 (hereinafter collectively referred to as actor icons W430). The time series chart W410 arranges the action icons W420 and actor icons W430 in chronological order from top to bottom. The order of the icons in the time series chart W410 is processed based on information indicating the date and time of the action, such as the posting date and time of the action history.

Different icons are set for the action icon W420 depending on the type of action history for the business. Action icons W421 and W425 indicate update actions such as registering, changing, and deleting business information or information associated with the business information (such as budget information). Action icons W422 and W424 indicate comment actions for business information. Action icons W426 and W427 indicate approval actions for business information. Action icons W423 and W428 indicate criticism actions for business.

The comment-related behavior icon W422 is generated based on the comment behavior. The generated behavior icon W422 generates a person icon W431 indicating the person who performed the comment behavior, and branches the chart starting from the comment behavior. A series of comment behaviors related to the comment behavior of the behavior icon W422 corresponds to a thread in the chat format. A thread is generated by replying to a comment.

In this embodiment, threads are classified into large threads that branch off from the comment-related behavior icon W422, and small threads that branch off from the comment behavior of a commenter in the large thread. Note that threads may further branch off depending on the comment behavior in the thread. Each of the actor icons W431 to W435 indicates a small thread that was generated by the comment behavior of a certain actor. The actor icon W430 displays the number of comments in the small thread in parallel.

The chart that branches off from the action icon W422 merges with the original chart, ending with the action of the actor represented by the actor icon W435. The end point is determined by the action of the actor, such as a completion instruction or approval action. The end point may also be determined automatically if a specified period of time has passed or if no comment action has been recorded for a specified period of time.

The action icon W423 relating to the pointed out action is generated based on the pointed out action. The generated action icon W423 generates a actor icon W436 indicating the actor of the pointed out action, and branches the chart starting from the pointed out action. The chart branched from the pointed out action displays the actor icon W437 of the actor who performed the comment action, as in the chart branched from the comment action. The chart branched from the action icon W424 merges with the original chart with the action of the actor icon W435 as the end point. Here, the end point is preferably an approval action by the actor in response to the pointed out action. The end point may be determined by a completion instruction by the actor after the approval action.

The action icons W426 and W427 relating to approval actions are generated based on approval actions. Here, the action icons W426 and W427 may be generated based on a predetermined approval action, such as approval of budget information associated with business information. In FIG. 22, the time series chart W410 shows, for example, the flow of action status for a series of business operations leading up to approval of budget information, and is used to grasp at a glance that an update action for registering budget information has occurred in the action icon W421, a pointing out action for the budget information has occurred in the action icon W423, an approval action for responding to the pointing out action has occurred, an update action for the budget information has occurred in response to the approval action, and an approval action for the budget information has occurred in the action icons W426 and W427.

Figure 23 shows an example of the screen display of the execution management screen W500 used to manage business operations in the execution stage. The execution management screen W500 includes a task evaluation item setting section W510, an execution observation report registration section W520, an execution status judgment report registration section W530, an innovation report registration section W540, and a request button W550.

The execution management screen W500 is used to manage execution actions and budget preparation actions related to budget revisions. In this embodiment, execution actions are recorded by completing tasks, registering execution observation reports, registering innovation reports, etc.

The task evaluation item setting unit W510 accepts the setting and registration of task evaluation items for administrative projects. Task evaluation items include task type, task name, task content, task completion date, completion report date, and an importance flag that can be set for important tasks. The completion report date is automatically entered as the date and time when the administrative project management device 2 acquires the execution action resulting from the completion of a task, and is displayed as the execution status.

The execution observation report registration unit W520 accepts the registration of execution observation reports that indicate execution actions for business operations. Execution observation reports include the report name of the execution action, the report content, and the report date. Execution observation reports are used to record the execution content of business operations as execution actions in a timely manner.

The execution status judgment report registration unit W530 accepts the registration of execution status judgment reports related to budget compilation actions for administrative projects. Execution status judgment reports are related to execution actions reported by execution observation reports, and report the results of budget correction judgments when execution problems arise as a result of the process. Execution status judgment reports correspond to budget correction actions related to budget correction, and include the report name related to the budget correction judgment, the report content, the report date, the related execution observation report that led to the judgment, a priority flag indicating the need for priority measures, the type of supplementary budget, and factors. Here, priority issue information may be generated by attaching the priority flag.

The innovation report registration unit W540 accepts the registration of innovation reports related to special executive actions for business operations. Innovation reports have a report title, issue significance, response content, outcome content, report date, and a candidate flag indicating whether the report is a candidate for intensive evaluation. Note that innovation reports may also include reports on executive actions for organizational or administrative activities by personnel not related to business operations.

When the request button W550 is pressed, the information entered in the task evaluation item setting unit W510, the execution observation report registration unit W520, the execution status judgment report registration unit W530, and the innovation report registration unit W540 is sent to the administrative business management device 2. Based on the received information, the action status output unit 30 outputs it as a notification to the user terminal 3 owned by the execution manager. In particular, the action status output unit 30 generates an execution status based on the execution action and the budget compilation action related to the budget correction instruction associated with the execution action, and can output a notification regarding the execution status to the execution manager indicating that a correction budget is required for the administrative business.

<Action status>
The behavior status output unit 30 outputs a behavior status in response to a request to output the behavior status.

In response to a request to output the indicated status, the behavior status output unit 30 outputs a list of indicated actions W200 as an example of the indicated status, as shown in FIG. 20(a). In response to a request to output the indicated status, the behavior status output unit 30 outputs a post of an indicated action W300 as an example of the indicated status, as shown in FIG. 21(a).

In response to a request to output the comment status, the behavior status output unit 30 outputs the comment behavior post W310 illustrated in FIG. 21(b) as the comment status.

In response to a request to output the approval status, the action status output unit 30 outputs the approval action post W320 illustrated in FIG. 21(c) as the approval status. In addition, in response to a request to output the approval status, the action status output unit 30 outputs the approval status including the number of approvals or the approval achievement rate of administrative tasks in a business group to which multiple administrative tasks and businesses belong. In addition, when one administrative task requires multiple approval actions, the approval status may be output as an indication of up to what stage the approval actions have been performed.

The action status output unit 30 outputs chat screens W330 and W340, exemplified in Figs. 21(d) and (e), in response to a request to output a chat screen for checking the action status for an administrative project. As described above, the chat screen outputs the indication status, comment status, and approval status in chat format based on at least one or more posted data of indication actions, comment actions, and approval actions.

The behavior status output unit 30 outputs a chart screen W400, as shown in FIG. 22, in response to a request to output a chart screen for checking the behavior status of an administrative project. As described above, the chart screen W400 outputs a behavior status in chart format, including at least one of a pointing out status, a comment status, and an approval status, based on a behavior history including at least one of a pointing out behavior, a comment behavior, and an approval behavior.

In response to a request to output the execution status, the action status output unit 30 outputs the registration information regarding the execution action illustrated in FIG. 23 as the execution status. In addition, in response to the registration of the budget compilation action related to the budget correction instruction, the action status output unit 30 generates the execution status and/or the budget compilation status, and outputs it as a notice to the execution manager. The action status output unit 30 preferably outputs both the execution status and the budget compilation status based on the budget compilation action that occurred in relation to the execution action.

The behavioral status output unit 30 outputs the behavioral status of each of the priority business projects and the general business projects based on the behavioral history for the priority business projects and the behavioral history for the general business projects, respectively. In particular, the behavioral history for the priority business projects includes a budget compilation action to compile a priority budget for the priority business projects and an approval action to approve the priority budget. In addition, the behavioral history for the general business projects includes a budget compilation action to compile a general budget for the general business projects and an approval action to approve the general budget.

The behavior status output unit 30 generates an output based on the answering behavior in response to a request to output the answering status. The behavior status output unit 30 generates an output based on the raising behavior, including the issue raising behavior and/or the policy system raising behavior, in response to a request to output the raising status. These outputs may be the results of aggregations by period, such as the number of answers, issue raisings, and policy system raisings. In addition, a request to output the raising status may be requested together with the specification of the target issue or the target policy system information, and the process of a series of administrative tasks related to the establishment of an issue or business, such as answers or execution of the factors of the issue, and issues that are factors in the establishment of the policy system, can be output as the raising status.

In addition, the behavior status output unit 30 outputs behavior status related to a policy system in response to a request to output a behavior status related to the policy system. For example, in response to a request to output a behavior status related to an administrative project, the behavior status output unit 30 can display a list of priority issues related to the target administrative project, responses that caused the priority issues, and the like.

Priority tasks and projects are preferentially allocated the general budget in addition to the priority budget. Therefore, general tasks and projects are allocated the remaining general budget after subtracting the general budget preferentially allocated to priority tasks and projects. The action history recording unit 28 reflects the priority budget in the budget information by acquiring the budget preparation action and approval action for the priority tasks and projects. The action status output unit 30 acquires the budget preparation action and approval action for the priority tasks and projects, and when the budget information is updated, generates a notification for acquiring the budget preparation action and approval action for the general tasks and projects, and transmits it to the user terminal 3 of the person in charge of the general tasks and projects. The action history recording unit 28 permits the acquisition of the budget preparation action and approval action for the general tasks and projects by acquiring the budget preparation action and approval action for the priority tasks and projects. This makes it possible to realize suitable support for administrative work that allocates the general budget to general tasks and projects after the general budget has been allocated to the priority tasks and projects.

Reference Signs List 1: Administrative business management system 2: Administrative business management device 21: Business registration unit 22: Group registration unit 23: Tag processing unit 24: Evaluation unit 25: Update unit 26: Search processing unit 27: Matching processing unit 28: Action history recording unit 29: Action history acquisition unit 30: Action status output unit 3: User terminal 4: Request destination terminal DB: Storage unit

Claims (16)

An administrative business management system,
The system includes a business registration unit, a behavior history acquisition unit, and a behavior status output unit,
The business registration department accepts registration of policy system information relating to at least policies, programs, and business programs established based on laws and regulations;
The behavior history acquisition unit acquires a behavior history related to the policy system information,
The behavior status output unit outputs a behavior status related to the policy, the program, or the business based on the behavior history,
The behavior history includes a pointing out behavior for the business, an approval behavior for the business, and a comment behavior,
The behavior history acquisition unit acquires the pointed out behavior by accepting post data in association with a pointed out element for the business, acquires the comment behavior by accepting post data in association with a comment corresponding to the pointed out behavior, and acquires the approval behavior by accepting post data in association with an approval instruction corresponding to the pointed out behavior;
The action status output unit outputs the approval status of the administrative business based on the approval action, and outputs the action status showing the icon of the actor in a time series chart based on the action history including the pointing out action, the comment action, and the approval action, and information indicating the actor who performed the action history. The administrative business management system according to claim 1 , wherein the action status output unit outputs an approval status including the number of approvals or the approval achievement rate in a group to which a plurality of tasks and businesses belong. The administrative business management system according to claim 1 , wherein the time series chart starts from the indicated behavior and ends with the approval behavior. An administrative business management system,
The system includes a business registration unit, a behavior history acquisition unit, and a behavior status output unit,
The business registration department accepts registration of policy system information relating to at least policies, programs, and business programs established based on laws and regulations;
The behavior history acquisition unit acquires a behavior history related to the policy system information,
The behavior status output unit outputs a behavior status related to the policy, the program, or the business based on the behavior history,
The action history includes enforcement actions against the business,
The action status includes the execution status of the business,
The action status output unit outputs the execution status of the administrative business based on the execution action , and is an administrative business management system. The administrative business management system according to claim 4 , wherein the action status output unit receives input of a budget correction instruction in association with at least one execution action, generates the execution status, and outputs it as a notice to an execution manager. An administrative business management system,
The system includes a business registration unit, a behavior history acquisition unit, and a behavior status output unit,
The business registration department accepts registration of policy system information relating to at least policies, programs, and business programs established based on laws and regulations;
The behavior history acquisition unit acquires a behavior history related to the policy system information,
The behavior status output unit outputs a behavior status related to the policy, the program, or the business based on the behavior history,
The action history includes an action history for a priority business and an action history for a general business,
The action status includes an action status for the priority business and an action status for the general business,
The action status output unit is an administrative business management system that outputs the action status of each of the priority business projects and the general business projects based on the action history for each of the priority business projects and the general business projects. The action history includes a budget preparation action for preparing a priority budget for the priority business and a general budget for the general business, and an approval action for the priority business and the general business;
The administrative business management system according to claim 6 , wherein the action status output unit generates a notification for acquiring budget preparation actions and approval actions for the general business by acquiring budget preparation actions and approval actions for the priority business. An administrative business management system,
The system includes a business registration unit, a behavior history acquisition unit, and a behavior status output unit,
The business registration department accepts registration of policy system information relating to at least policies, programs, and business programs established based on laws and regulations;
The behavior history acquisition unit acquires a behavior history related to the policy system information,
The behavior status output unit outputs a behavior status related to the policy, the program, or the business based on the behavior history,
The action history includes actions to raise issues based on factors of response or execution, and policies, measures, and business projects based on the issues,
The action status output unit outputs the process related to the establishment of the issue or the policy, measure, or business as the action taken based on the action taken and the designation of the issue or the policy, measure, or business , as the action taken status. 1. A method for managing administrative operations, comprising:
A process of accepting registration of policy system information relating to at least policies, programs, and business projects established based on laws and regulations;
acquiring a behavior history related to the policy system information;
and outputting a behavioral status related to the policy, the program, or the business based on the behavioral history ,
The behavior history includes a pointing out behavior for the business, an approval behavior for the business, and a comment behavior,
The step of acquiring the behavior history includes acquiring the pointed-out behavior by accepting post data in association with a pointed-out element for the business, and acquiring the comment behavior by accepting the post data in association with a comment corresponding to the pointed-out behavior;
Acquire the approval action by receiving the posting data in association with an approval instruction corresponding to the indicated action;
The step of outputting the behavioral status is an administrative business management method in which the approval status of the administrative business is output based on the approval behavior, and the behavioral status is output showing the icon of the actor in a time series chart based on the behavioral history including the pointing out behavior, the comment behavior, and the approval behavior, and information indicating the actor who performed the behavioral history . A government business management program comprising:
A computer is caused to function as a business registration unit, a behavior history acquisition unit, and a behavior status output unit;
The business registration department accepts registration of policy system information relating to at least policies, programs, and business programs established based on laws and regulations;
The behavior history acquisition unit acquires a behavior history related to the policy system information,
The behavior status output unit outputs a behavior status related to the policy, the program, or the business based on the behavior history,
The behavior history includes a pointing out behavior for the business, an approval behavior for the business, and a comment behavior,
The behavior history acquisition unit acquires the pointed-out behavior by accepting post data in association with a pointed-out element for the business, and acquires the comment behavior by accepting post data in association with a comment corresponding to the pointed-out behavior;
Acquire the approval action by receiving the posting data in association with an approval instruction corresponding to the indicated action;
The administrative business management program, wherein the behavior status output unit outputs the approval status of the administrative business based on the approval behavior, and outputs the behavior status showing the icon of the actor in a time series chart based on the behavior history including the pointing out behavior, the comment behavior, and the approval behavior, and information indicating the actor who performed the behavior history . 1. A method for managing administrative operations, comprising:
A process of accepting registration of policy system information relating to at least policies, programs, and business projects established based on laws and regulations;
acquiring a behavior history related to the policy system information;
and outputting a behavioral status related to the policy, the program, or the business based on the behavioral history,
The action history includes enforcement actions against the business,
The action status includes the execution status of the business,
The step of outputting the action status outputs the execution status of the administrative business based on the execution action, in the administrative business management method. A government business management program comprising:
A computer is caused to function as a business registration unit, a behavior history acquisition unit, and a behavior status output unit;
The business registration department accepts registration of policy system information relating to at least policies, programs, and business programs established based on laws and regulations;
The behavior history acquisition unit acquires a behavior history related to the policy system information,
The behavior status output unit outputs a behavior status related to the policy, the program, or the business based on the behavior history,
The action history includes enforcement actions against the business,
The action status includes the execution status of the business,
The action status output unit outputs the execution status of the administrative business based on the execution action, and is an administrative business management program. 1. A method for managing administrative operations, comprising:
A process of accepting registration of policy system information relating to at least policies, programs, and business projects established based on laws and regulations;
acquiring a behavior history related to the policy system information;
and outputting a behavioral status related to the policy, the program, or the business based on the behavioral history,
The action history includes an action history for a priority business and an action history for a general business,
The action status includes an action status for the priority business and an action status for the general business,
The step of outputting the behavioral status of the administrative business management method includes outputting the behavioral status of each of the priority business and the general business based on the behavioral history of each of the priority business and the general business. A government business management program comprising:
A computer is caused to function as a business registration unit, a behavior history acquisition unit, and a behavior status output unit;
The business registration department accepts registration of policy system information relating to at least policies, programs, and business programs established based on laws and regulations;
The behavior history acquisition unit acquires a behavior history related to the policy system information,
The behavior status output unit outputs a behavior status related to the policy, the program, or the business based on the behavior history,
The action history includes an action history for a priority business and an action history for a general business,
The action status includes an action status for the priority business and an action status for the general business,
The action status output unit is an administrative business management program that outputs the action status of each of the priority business projects and the general business projects based on the action history of each of the priority business projects and the general business projects. 1. A method for managing administrative operations, comprising:
A process of accepting registration of policy system information relating to at least policies, programs, and business projects established based on laws and regulations;
acquiring a behavior history related to the policy system information;
and outputting a behavioral status related to the policy, the program, or the business based on the behavioral history,
The action history includes actions to raise issues based on factors of response or execution, and policies, measures, and business projects based on the issues,
The step of outputting the action status is an administrative business management method in which the process outputs the process related to the establishment of the issue or the policy, measure, or business as a proposing status based on the proposing action and the designation of the issue or the policy, measure, or business. A government business management program comprising:
A computer is caused to function as a business registration unit, a behavior history acquisition unit, and a behavior status output unit;
The business registration department accepts registration of policy system information relating to at least policies, programs, and business programs established based on laws and regulations;
The behavior history acquisition unit acquires a behavior history related to the policy system information,
The behavior status output unit outputs a behavior status related to the policy, the program, or the business based on the behavior history,
The action history includes actions to raise issues based on factors of response or execution, and policies, measures, and business projects based on the issues,
The action status output unit outputs the process related to the establishment of the issue or the policy, measure, or business as a proposing status based on the proposing action and the designation of the issue or the policy, measure, or business, an administrative business management program.