Administrative project management system, administrative project management method, and administrative project management program

Abstract

To provide assistance in realizing centralized macro evaluation by grouping administrative projects.SOLUTION: An administrative project management system disclosed herein is configured to receive registration of administrative project information regarding administrative projects established on the basis of laws and regulations, associate the administrative project information with project group information related to administrative projects based on classification conditions, and output evaluation results for the administrative projects on the basis of evaluation axes associated with project groups.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to an administrative business management system, an administrative business management method, and an administrative business management program. [Background technology]

[0002] In the finances of local governments, etc., budgets are compiled from limited financial resources and used to implement projects. The administrative tasks and projects of local governments are diverse, and in order to compile budgets efficiently for them, it is necessary to properly evaluate the administrative tasks and projects.

[0003] Patent Document 1 discloses a technology that can efficiently support a local government 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 the 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 the performance indicator level corresponding to the indicator of the administrative business from the administrative evaluation indicator database and generating administrative evaluation candidate indicator information storing the performance indicator level, and a step of outputting the generated administrative evaluation candidate indicator information.

[0004] Patent Document 2 discloses a technique for simplifying the processing of the financial department involved in budget assessment and administrative reform planning, and for realizing budget assessment and long-term financial estimates that are in line with the actual conditions of each task and project. Specifically, Patent Document 2 discloses a technique that includes a step of aggregating annual planned values ​​for each task and project, which aggregates annual planned values ​​for costs and financial resources entered in a task and project sheet, a step of calculating estimates for each expense item based on objective estimates for tasks and projects that do not create revenue information or task and project sheets, a step of estimating specific expenses, a step of selecting an estimation method to be performed for each revenue and expenditure item, and a step of estimating a mid- to long-term financial outlook that estimates a mid- to long-term financial outlook based on the plan for each individual task and project from the estimation results based on the method selected in the estimation method selection step. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2002-334185 A [Patent Document 2] JP 2005-293321 A Summary of the Invention [Problem to be solved by the invention]

[0006] On the other hand, the administrative tasks and projects in local governments are diverse, and there were no standards for unified evaluation of them. Therefore, in order to evaluate how much budget was allocated to what kind of tasks and projects, and how much performance was achieved against the budget, it was necessary to check the administrative evaluation reports of individual tasks and projects. In addition, when selecting tasks and projects for budget compilation, it was complicated to manage and evaluate what criteria should be used for selection, when should the selection be made, who should make the selection, etc., and high costs were incurred in carrying out these tasks.

[0007] The present invention has been made in consideration of the above-mentioned problems, and an object of the present invention is to provide a technique for supporting a centralized macro evaluation by grouping business operations. [Means for solving the problem]

[0008] In order to solve the problems described above, the present invention provides an administrative business management system comprising a business registration unit, a group registration unit, and an evaluation unit, wherein the business registration unit accepts registration of business information relating to business affairs established based on laws and regulations, the group registration unit associates the business affairs information with business group information related to the business affairs based on classification conditions, and the evaluation unit outputs evaluation results of the business affairs based on evaluation axes associated with the business group information.

[0009] The present invention also provides an administrative business management method, in which a computer executes the steps of accepting registration of business information relating to business affairs established based on laws and regulations, associating the business information with business group information related to the business affairs based on classification conditions, and outputting evaluation results of the business affairs based on evaluation axes associated with the business group information.

[0010] The present invention also provides an administrative business management program that causes a computer to function as a business registration unit, a group registration unit, and an evaluation unit, wherein the business registration unit accepts registration of business information relating to administrative businesses established based on laws and regulations, the group registration unit associates the administrative business information with business group information related to the administrative business based on classification conditions, and the evaluation unit outputs evaluation results of the administrative business based on evaluation axes associated with the business group information.

[0011] Such a configuration allows businesses to be grouped and evaluated macroscopically using the evaluation axis associated with the group.

[0012] In a preferred embodiment of the present invention, the evaluation section outputs an evaluation result for each business group based on an evaluation axis associated with the business group information. This structure allows businesses to be evaluated on a macro level on a business group basis.

[0013] In a preferred form of the present invention, the administrative and business information is capable of setting a progress status according to the processing stage, the evaluation axis is the progress status for each stage of the progress status, and the evaluation unit outputs an evaluation result regarding the progress status in the business group. In a preferred embodiment of the present invention, the evaluation unit outputs an evaluation result regarding the progress status based on the total number of pieces of business information belonging to the business group information and the number of pieces of business information having a predetermined progress status. With this configuration, progress within the group can be evaluated, and progress management of administrative work can be made more efficient.

[0014] In a preferred form of the present invention, the administrative business information includes budget information including a budget amount and a revenue amount, the business group information includes a total budget amount and a total revenue amount based on the budget information, and the group registration unit accepts registration of a budget allocation amount based on the total budget amount and the total revenue amount. By adopting such a configuration, it is possible to efficiently organize budget allocation amounts for groups.

[0015] In a preferred form of the present invention, the administrative business information includes budget information including a budget amount and / or a revenue amount, the business group information includes a total budget amount and / or a total revenue amount based on the budget information, the evaluation axis is the progress of the total budget amount and / or the total revenue amount, and the evaluation unit outputs an evaluation result regarding the progress in the business group. This configuration makes it possible to evaluate the progress of changes in budgets and financial resources, and to streamline the compilation of budgets and projects.

[0016] In a preferred embodiment of the present invention, the group registration unit receives an instruction operation including a person in charge of the business group information, and outputs an instruction notification including access information for the business group information to the person in charge. With this configuration, instructions can be easily given with reference to the group.

[0017] In a preferred form of the present invention, the administrative business information has evaluation items including quantitative evaluation items and / or task evaluation items and goals for those, the evaluation axis is the status of achievement of the goals, and the evaluation unit outputs evaluation results regarding the status of achievement in the business group. Such a configuration allows for a macro evaluation of the progress of a group's goals.

[0018] In a preferred embodiment of the present invention, a tag processing unit is provided for associating tag information with the business / task information or the business group information, and the evaluation unit outputs an evaluation result of the business / task based on the tag information. In a preferred embodiment of the present invention, the evaluation axis is a distribution state of the tag information, and the evaluation unit outputs an evaluation result regarding the distribution state of the tag information in the business group. In a preferred embodiment of the present invention, the tag processing unit outputs a classification result of the tag information related to the business on the basis of a business summary included in the business information. In a preferred embodiment of the present invention, the tag information includes an organization tag and a business tag, and a search processing unit is provided for acquiring business and administrative information having different organization tags but a common business tag. In a preferred form of the present invention, the tag information has a granularity level including policies, measures, and administrative / business operations, the evaluation axis is progress, progress, achievement, or distribution, and the evaluation unit outputs evaluation results for each of the policy unit, measure unit, and administrative / business unit. With this configuration, it is possible to use tags to manage businesses and the like through unified classification.

[0019] In a preferred embodiment of the present invention, the matching processing unit accepts public recruitment information for a business including an organizational classification and a business classification, accepts application information for the business including the organizational classification and the business classification, and performs a matching process between the public recruitment information and the application information. In a preferred embodiment of the present invention, the matching processing unit executes a process of allowing the recruiting organization to approve application information for the public recruitment information, or a process of allowing the applicant organization to approve the public recruitment information for the application information. With this configuration, it is possible to provide a platform that supports the matching of public recruitment and applications for administrative projects. Effect of the Invention

[0020] According to the present invention, it is possible to provide a technique for supporting a centralized macro evaluation by grouping business operations. [Brief description of the drawings]

[0021] [Figure 1] FIG. 1 is a system configuration diagram of the present embodiment. [Diagram 2] FIG. 2 is a diagram showing the hardware configuration of the present embodiment. [Diagram 3] 3 is a process flowchart of the present embodiment. [Figure 4] 4 shows an example of a data configuration according to the present embodiment. [Diagram 5] 13 shows a display example of a group management screen according to the embodiment. [Figure 6] 13 shows a display example of a progress information creation screen and an instruction notification according to the embodiment. [Figure 7] 13 shows a display example of a group formation screen according to the present embodiment. [Figure 8] 13 shows a display example of a group formation screen according to the present embodiment. [Figure 9] 13 is a display example of a budget allocation registration screen according to the embodiment. [Figure 10] 4 is a process flowchart of the budget compilation stage of the present embodiment. [Figure 11] 13 shows a display example of a tag processing screen according to the embodiment. [Figure 12]FIG. 4 is a schematic diagram of tag information according to the embodiment. [Figure 13] 2 shows an example of the configuration of a classification model according to the present embodiment. [Figure 14] 13 shows a display example of a comparison evaluation screen according to the present embodiment. [Figure 15] 13 shows a display example of a matching screen according to the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0022] The administrative business management system, method, and program of the present invention will be described below 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 shown below, and various configurations can be adopted.

[0023] In this embodiment, the configuration, operation, etc. of the administrative project management system will be described, but a similarly configured method, device, computer program, and program recording medium storing the program can also achieve the same 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 a flexible disk, or even via a communication line.

[0024] 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 with the arithmetic device. The administrative business management method is realized by processing of the computer device including the administrative business management device.

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

[0026] 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. Administrative projects are implemented by each bureau belonging to the administrative division based on the budget of each bureau. Note that the classifications of policy, measure, administrative work, etc. are not limited to these, and further classifications such as detailed measures may be established.

[0027] In this embodiment, the main explanation is for a system that uses an administrative business management system to support administrative work at each stage, such as the planning stage, budget preparation stage, execution stage, and evaluation stage of an administrative business. At the planning stage, a plan for the administrative business to be implemented in the execution year (e.g., the following year) of the target administrative business is prepared. At the budget preparation stage, a budget request for the administrative business related to the plan is prepared, and a financial assessment of the budget request is carried out. At the execution stage, administrative businesses that have passed the assessment are executed. At the assessment stage, an administrative assessment report for the executed administrative business 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.

[0028] <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.

[0029] The administrative project management device 2 comprises, as functional components, a project 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.

[0030] The user terminal 3 is a terminal device operated by a user at each office of an administrative division of a local government, etc. Although only one user terminal 3 is shown in Fig. 1, a plurality of user terminals 3 are installed in each local government. Also, there may be a plurality of local governments.

[0031] 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 plans for administrative projects, 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 the budget requests. Managers perform tasks such as selecting key projects based on plans, prioritizing, and assessing budget requests approved by financial officers. The administrative project management system 1 provides each user with predetermined operating authority, and controls the permission and restriction of predetermined functions according to the operating authority.

[0032] The request destination terminal 4 is a terminal device operated by a request destination of a government-contracted business or 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, a plurality of request destination terminals may exist.

[0033] The storage unit DB is not limited to the configuration shown in Fig. 1 as long as it is a database and is configured to be capable of data communication with the administrative business management device 2. For example, the storage unit DB may be built into the administrative business management device 2, or may be installed outside the administrative business management device 2 and connected to it by wire for communication. 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.

[0034] Fig. 2(a) shows a hardware configuration diagram of the administrative business management device 2. The administrative business management device 2 includes, as its hardware configuration, a control unit 201, a storage unit 202, and a communication unit 203. 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 configured with a plurality of computer devices, and is not limited to the configuration shown in Fig. 2(a) as long as the above-mentioned functional components (21-27) can be realized as a whole.

[0035] The control unit 201 is configured with one or more processors such as a CPU, and controls the overall processing in the administrative business management device 2 by executing an administrative business management program, an OS (Operating System), and other applications. The storage unit 202 is a hard disk drive (HDD), a solid state drive (SSD), a flash memory, a RAM (Random Access Memory), or the like, 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 storage 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.

[0036] 2(b) shows a hardware configuration diagram of a terminal device 9 including the user terminal 3 and the 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.

[0037] 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 an 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 an operator, and is composed of a touch panel, a mouse, a keyboard, etc. The display unit 905 is composed of a display that displays the processing results by the control unit 901, etc.

[0038] 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.

[0039] In 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 the 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).

[0040] 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. When 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.

[0041] 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.

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

[0043] <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 it in the storage unit DB. The business information may be acquired from a database installed in each local government.

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

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

[0046] 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 created for each execution year, and is stored in the storage unit DB in association with the business information.

[0047] The 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 the goal.

[0048] 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 achievement of the target is evaluated based on the actual results against the set target. Multiple quantitative evaluation items may be set.

[0049] A task evaluation item is an evaluation item that can be evaluated based on the achievement of a set task. A task evaluation item is set as an arbitrary task name or task content, 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 performance against the set goal. The performance of a task evaluation item is input as whether the task is completed, whether the task is completed within the schedule, etc. A plurality of task evaluation items may be set. Furthermore, the task evaluation item may be capable of setting an important task from among the set tasks, and the achievement status of each goal of an important task and a normal task can be evaluated.

[0050] 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 budget, priority budget, and management budget. 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.

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

[0052] 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.

[0053] As shown in FIG. 4(e), the evaluation information has an execution year and actual results, with an evaluation ID as a key. 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 ​​for target values ​​such as KPI and KGI, 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 target business or project. In addition, the administrative evaluation report of the business or project in the target year may be stored in the storage unit DB in association with the evaluation information.

[0054] <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.

[0055] 5(a) shows an example of a group management screen W1 displayed on the user terminal 3. The group management screen W1 includes 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.

[0056] The summary display section W11 displays the setting status of the frame, the frame amount, and the requested amount. The frame indicates the frame of the amount that can be requested. In the example of Fig. 5(a), 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 the 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 are displayed.

[0057] The group list display unit W12 displays a list of business group information. The group list display unit W12 also displays a list of group IDs, business group names, persons in charge, progress, categories, deadlines, total business costs, and budgets based on the business group information and various information associated with the business group information. The progress status displays 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 tasks and projects belonging to the business group and the quantity of tasks and projects having a specified progress status.

[0058] When an input operation is received by pressing the new group creation button W13, a group creation screen W2 is displayed on the user terminal 3 as shown in FIG. 5(b).

[0059] 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 a 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 input in the group information input section W21 as business group information is transmitted to the administrative business management device 2.

[0060] As shown in Fig. 4(f), the business group information has a business group name and a business ID of one or more business operations associated with the business group, with the business group ID as a key. The business group information may also include a category 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.

[0061] In one embodiment, the business group information is configured so that the user can register any task and business information in association with it. The group name of the business group information is determined according to any classification condition set by the user. Here, the classification condition includes a category selected by the user. In addition to the category, any classification condition may be appropriately set according to the purpose of grouping set by the user.

[0062] As a specific example, when creating a group for organizing budgetary frameworks 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 administrative projects that are to be prioritized, 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 administrative 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.

[0063] In one embodiment, the business group information and the administrative / business information each have classification conditions. The business group information is configured to be automatically registered in association with administrative / business information to which similar classification conditions have been assigned. The memory unit DB stores master information of the classification conditions. The administrative / 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 / business information. Furthermore, the classification conditions may correspond to tag information, which will be described later.

[0064] 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 construction, 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, an administrative project, etc., and has subclassifications such as a specific policy name, a measure name, and an administrative project name. Settlement statistics / purpose classification is a classification related to settlement statistics or purpose, and has subclassifications such as a specific settlement statistics name and purpose type. Organization classification is a classification such as a department or section in an organizational chart, and has subclassifications such as a specific department name and section name. Nature classification is a classification related to the breakdown of revenue or expenditure, and has subclassifications such as property expenses, public construction, subsidy, prefectural management, personnel expenses, subsidy, and subsidy grants. Note that classification conditions are not limited to these and may be set appropriately depending on the purpose.

[0065] 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.

[0066] When the registration button W32 is pressed, a registration instruction for the progress information is transmitted to the administrative project management device 2. The administrative project management device 2 stores the progress information in the storage unit DB.

[0067] The progress information is used to manage the progress of the business operations belonging to the 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 organization and deadlines.

[0068] When the group registration unit 22 receives an instruction operation including an instruction to a person in charge of 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.

[0069] FIG. 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, person in charge ID, etc. The person in charge who receives the instruction notification can access the group organization screen and organize the business group.

[0070] When the progress information is registered, the evaluation unit 24 executes an evaluation process with the progress status as an evaluation axis based on the business group information associated with the progress information and the progress status of the 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 aggregate the progress status of the business operations belonging to the business group by stage and output the evaluation result regarding the progress status of each business operation with respect to the entire business group. The aggregated result of the progress status is shown, for example, by the ratio or total number by status. The evaluation result regarding the progress status is 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.

[0071] The progress status of administrative business information is a status that indicates the processing stage according to the category. The progress status at the planning stage is further classified into detailed stages such as before submission of the business plan and submitted. The progress status at the budget preparation stage is further classified into detailed stages such as before requesting a budget request, requested and assessed. The progress status at the execution stage is further classified into detailed stages such as before execution, in execution and completed. The progress status at the evaluation stage is further classified into detailed stages such as before submission of the administrative evaluation report and submitted. The progress status is updated by accepting setting operations via the user terminal 3 according to the processing stage.

[0072] <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.

[0073] 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 notice. The group formation screen W4 may also be displayed by pressing a details button on the group management screen W1. Here, an example will be described in which, at the budget formation stage, a person in charge of an original department who has received an instruction notice regarding a request to prepare 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.

[0074] 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 switch between display and non-display 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.

[0075] The search unit W43 provides a function for searching for 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 business operation 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.

[0076] The search unit W43 can use, as search conditions, the execution year, business group, budget category such as initial budget / supplementary budget, predetermined keywords, classification conditions, tag names, past KPIs and budget-related results, etc. The KPIs and budget-related results are set by specifying a predetermined period and the rate of increase / decrease of the KPIs and budget, etc. The person in charge of the original section refers to the instruction notice and selects the administrative business to be added, changed or deleted from the business group.

[0077] 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. In addition, the search unit W43 may 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 amount, and the like.

[0078] The business display section W44 displays a list of business tasks that are candidates for addition to the business group, based on the business task information acquired as a search result by the search processing section 26. The add buttons W441A to W441C of the business display section W44 receive a selection operation of a business task to be added to the business group.

[0079] The candidate display section W421 of the group formation section W42 displays the administrative tasks and businesses that are candidates for the group selected by the add button W441. When the group creation button W422 is pressed, the administrative tasks and businesses displayed in the candidate display section W421 are registered as a business group. 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 tasks and businesses that belong to the business group.

[0080] The evaluation result display unit W411 displays the evaluation results of the business group. Here, the evaluation results include the total budget amount and the average budget amount of the business projects belonging to the business group. The evaluation results can be displayed in a manner that distinguishes the total budget amount and the 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, and the like with the budget amount of the target business group.

[0081] The switching unit W412 can switch the evaluation axis by accepting a selection operation and update the evaluation result displayed on 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.

[0082] In one embodiment, 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 financial resource type, 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.

[0083] As one embodiment, the evaluation result display section 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.

[0084] The summary display unit W41 outputs the 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 adding or deleting, 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 favorably supports the selection of administrative businesses to be associated with a business group while referring to the evaluation results.

[0085] <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 amount 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.

[0086] FIG. 10 shows an embodiment of the processing flow at the budget compilation stage. The administrative business management device 2 accepts a registration request for progress information via the user terminal 3 of the financial officer (S21). In S21, the registration request may include a registration request for 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 for associating budgetary information with business group information via the user terminal 3 of the financial officer (S22). Note that the steps of S21 and S22 may be interchanged. The original section person in charge selects the business information to be associated with the business group information while referring to the budget information, the budgetary information, the 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 information while referring to the budgetary information and the evaluation results. The administrative business management device 2 receives, via the user terminal 3 of the original department staff, an instruction to register business information to be associated with business group information, and an instruction to register budget information (S23). The financial staff and / or manager decides whether to approve or disapprove the budget information by referring to the budget information, budgetary 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 making it possible to realize progress management by business group.

[0087] <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 them 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).

[0088] The tag information may further include a granularity level indicating whether the tagged target corresponds to a policy, a measure, a minor measure, or an administrative project. In this embodiment, the tag information is configured, for example, as a hierarchical classification according to the granularity level. The 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, and agriculture, forestry, and fisheries. The 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 industry. The 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.

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

[0090] The granularity level may be set for tags that can be hierarchically classified. That is, the granularity level may be a hierarchical classification other than policy, measure, sub-measure, and business.

[0091] The tag information may be set with tags related to the fiscal year, organization, business, budget, priority issues, achievements, etc. Furthermore, the tag information may be set with tags corresponding to classification conditions stored as master information. For example, the tag information may 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.

[0092] When registering or editing business / business information and / or business group information, the tag processing unit 23 selects a tag ID or tag name corresponding to the business / business, and stores the selected tag ID or tag name in the storage unit DB in association with the business / business information.

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

[0094] The classification model is a model that is machine-learned using a data set. The model may be a known model such as a neural network, a logistic regression, a decision tree, or a 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.

[0095] The dataset used for machine learning of the model includes text data included 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 a classification result for any input of text data.

[0096] The storage 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 by the machine learning processing. The storage unit DB acquires and stores the generated classification model.

[0097] 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 input business. This allows for more appropriate tag information to be assigned.

[0098] 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 the 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, a process of associating a tag ID with a likelihood equal to or greater than a predetermined value with business information, and the like.

[0099] Fig. 11 shows examples of the tag processing screens W6A and W6B displayed on the user terminal 3. In Fig. 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 an input operation of text data included in the business information. The tag display section W62 displays tag names and the like based on tag IDs already assigned to the business information. The model selection section W63 accepts an operation of selecting a classification model to input the text data input to the text input section W61.

[0100] When a classification model is selected using the model selection unit W63 in Fig. 11(a), the screen is updated and displayed as a 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 to the selected classification model and obtains the tag ID output from the classification model.

[0101] The classification result display unit W64 displays the tag IDs that are the classification results, the tag names identified based on the tag IDs, the granularity level, and the likelihoods (scores). The classification result display unit W64 supports 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.

[0102] 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 associations, the number of keywords and the number of characters included in the text data, etc. By displaying the details of the classification process, the details display unit W65 contributes to preventing 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, the details display unit W65 contributes to supporting the determination of the tag information to be finally assigned.

[0103] The tag information is used for evaluation based on an evaluation axis regarding the distribution of the 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 the tag information assigned to the business and project information belonging to the business group information. The distribution indicates the total number of each piece of tag information within the business group, etc. The distribution indicates, for example, how many policies, measures, and projects are associated with each other within the business group.

[0104] <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.

[0105] Fig. 12(a) shows an example of the data structure of tag information, which includes a tag ID, a tag name, a granularity level, and a related tag ID.

[0106] In this embodiment, the granularity levels are at least three hierarchies, namely, policies, measures, and business operations. The granularity levels may 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.

[0107] 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 as a hierarchy from top to bottom in the order of policy tag, measure tag, and business tag. For example, the measure tag is defined by associating the tag ID of one policy tag as a related tag ID, and the business tag is defined by associating the tag ID of one measure tag as a related tag ID. Note that the measure tag may be defined by associating the tag ID of one or more business tags as a related tag ID, and the policy tag may be defined by associating the tag ID of one or more measure tags as a related tag ID.

[0108] 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 have the tag ID of the associated tag as the related tag ID.

[0109] Ancillary tags serve to add associated data to related basic tags. Ancillary tags are classified into cost tags, organization tags, fiscal year tags, performance tags, priority issue tags, and the like. Ancillary tags are added, for example, when an administrative project includes associated data related to revenues and / or expenditures, such as individual expenses and specific financial resources. An organization tag is added, for example, when an administrative project includes associated data related to an executive organization of a policy, measure, administrative project, and the like related to a basic tag. An executive organization may indicate a department or section within an organization, or the organization itself, such as each 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.

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

[0111] In this embodiment, the storage unit DB stores information such as policy information, program information, and business / project information that corresponds to the hierarchy of tag information such as policy tags, program tags, and business / project tags. As shown in Fig. 4(a), 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 policy basic 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, respectively. For example, the policy information may have associated program IDs, and the program information may have associated business / project IDs.

[0112] The policy information is configured to be able to tally up the total budget amount, total revenue amount, etc. for a policy based on the budget information of one or more associated business / project information. The policy information is configured to be able to tally up the total budget amount, total revenue amount, etc. for a policy based on the total budget amount and total revenue amount of one or more associated policy information.

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

[0114] In this embodiment, the tag processing unit 23 inputs text data related to an outline of a policy, a measure, or an administrative project into a classification model, and obtains a 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 data set. In this embodiment, the model may be a neural network, a regression model, a decision tree, a k-nearest neighbor model, or the like.

[0115] 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.

[0116] In this embodiment, the classification model has a plurality of classifiers, each of which outputs a classification result for an input, and is provided at least one at each level of tag information, and passes the output of the classification result to a classifier provided at the next level.

[0117] Fig. 13 shows an example of the configuration of the classification model M in this embodiment. According to Fig. 13, the classification model M includes a first classifier MA1 that receives input of text data related to an outline of a policy, a measure, or an administrative 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 measure 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 an administrative 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 may be configured according to the number of hierarchical levels.

[0118] The classification model M may be configured to include an associated tag classifier that receives input of text data related to an outline of a policy, a measure, or an administrative project, and outputs a classification result of the associated tag. The associated tag classifier may be configured to receive input of the classification results by the first to third classifiers, and output the classification result of the associated tag.

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

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

[0121] 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.

[0122] 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 specified 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.

[0123] The classifier identifies at least one of the above patterns based on a threshold set in the likelihood distribution, and determines whether or not 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, a tag that is highly likely to be tag information of a higher hierarchy, such as a policy tag or a measure tag.

[0124] 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 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 result, and outputs the classification result including the action tag C1 and the likelihood 0.75 to the classifier MC1, and the classification result including the action tag C2 and the likelihood 0.25 to the classifier MC2. The classifier MC1 receives an input of the classification results, and outputs a classification result including the business / business tag A and a likelihood of 0.88, and a classification result including the business / business 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 / business tag C and a likelihood of 0.58, and a classification result including the business / business tag D and a likelihood of 0.42. Here, for example, a threshold value of 0.5 is set for the likelihood distribution in classifiers MC1 and MC2, and classifier MC1 identifies the likelihood distribution as pattern 1 and outputs the business tag A and the business 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 the business / business tag A, the business / business tag B, the policy tag C2, and their respective likelihoods as classification results. 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).

[0125] 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 embodiment, 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. As one aspect, when the tag name displayed includes the business / business tag A that is finally output via classifier MA1, classifier MB1, and classifier MC1, it can be only the final output business / business tag A. Even if the likelihood of the business / business tag A is smaller than the likelihood of the policy tag B1 or the measure tag C1, if the likelihood distribution described above is pattern 1, it is highly likely to be the tag name output by a lower-level classifier. This makes it possible to make the selection and determination of tag names more efficient.

[0126] The classification model M can classify the associated tags in the same manner. For example, the classification model M outputs the classification result of the associated tags by inputting the classification results of each classifier to a classifier for the associated tags. Also, the associated tags may be classified using different classification models for classifying the associated tags.

[0127] 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.

[0128] 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.

[0129] Specifically, the search processor 26 accepts at least a basic tag specification operation, and acquires task and business information so as to include task and business information associated with tag information that has the same basic tag but does not have the same organization tag. Here, the organization tag includes tags of executive organizations such as different local governments, and the search processor 26 can search for information including task and business information to which organization tags of different local governments have been assigned. This allows information on policies, measures, and tasks and businesses, 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.

[0130] <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 operation 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.

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

[0132] 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 in setting the classification conditions (particularly, business classification) of the business group information.

[0133] The search function for business information may be provided to the terminal devices of local residents, which can support the provision of highly transparent business information to local residents.

[0134] A specific embodiment of the administrative project management system 1 will be described below.

[0135] <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 administrator, 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.

[0136] The administrative project management device 2 may accept an operation for assigning a priority to assessed task / project information via the administrator's user terminal 3, and store the priority in the storage unit DB in association with the task / project information.

[0137] <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." When the update unit 25 acquires an approval instruction for the budget information corresponding to the submitted budget request, it updates the progress status from "requested" to "assessed." 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 "execution stage."

[0138] When accepting an operation to give approval or disapproval to a budget request, the administrative project management device 2 can provide the priority order associated with each task / project information to the user terminal 3 of the approver (financial officer, manager). This allows the approver to, for example, assess tasks / projects in order of priority while referring to the priority order.

[0139] <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.

[0140] <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.

[0141] In this embodiment, in the execution stage or administrative evaluation stage, the administrative business management device 2 can accept inputs related to the results in the business information. The administrative business management device 2 accepts inputs of quantitative evaluation results corresponding to quantitative evaluation items as results values. The administrative business management device 2 accepts inputs of task evaluation results corresponding to task evaluation items by updating the status of completed tasks to completed.

[0142] <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 receiving a request for a specific evaluation result via the user terminal 3.

[0143] The evaluation unit 24 outputs the evaluation result of the business operation based on the evaluation axis associated with the business group information. The evaluation unit 24 also outputs the evaluation result for each business group based on the evaluation axis associated with the business group information.

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

[0145] The progress evaluation axis is used to evaluate the progress at each stage of progress status. The evaluation unit 24 outputs an evaluation result regarding the progress 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 is output, such as the ratio or total number by progress status relative to 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.

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

[0147] The evaluation axis of achievement status is used to evaluate the achievement status of the goals set in the quantitative evaluation items and task evaluation items. The evaluation unit 24 evaluates the achievement status of the business / project information based on the actual results input as the quantitative evaluation results for the target values ​​such as KPI and KGI set in the quantitative evaluation items. Here, the achievement status of each piece of business / project information indicates whether the actual results exceeded the target values, the achievement rate of the actual results against the target values, etc.

[0148] The evaluation unit 24 evaluates the achievement status of the business / project information based on the status regarding the completion of the task input as the task evaluation result for the task set in the task evaluation item. Here, the achievement status of each piece of business / project information indicates whether the task was completed, whether the task was completed within the schedule, the achievement rate for multiple tasks, etc. The evaluation unit 24 may evaluate the achievement status for each of the normal tasks and the important tasks.

[0149] The evaluation unit 24 evaluates the achievement status of the goal of the entire business group based on the achievement status of the individual business information associated with the business group information. Here, the achievement status of the business group indicates the average achievement rate of the business, the total number of achievements and achievement rate of the goal, the total number of achievements and achievement rate of each of the normal tasks and the priority tasks, etc.

[0150] The achievement status may indicate a change in the achievement status of the goal. In this case, the achievement status is output in the form of a graph, table, or map showing, for example, the change in the achievement rate of the goal or the change in the number of achievements since a specified year.

[0151] The evaluation axis of the distribution situation is used to evaluate the distribution situation of the tag information. The evaluation unit 24 counts each tag ID assigned to the business operations belonging to the business group. The evaluation unit 24 outputs the quantity of each tag ID based on the counted tag ID as an evaluation result regarding the distribution situation. Here, the evaluation result regarding the distribution situation may be output in a form such as a graph of the quantity for each tag ID.

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

[0153] The evaluation unit 24 can output the evaluation results in a comparable manner for each policy unit, each policy unit, each sub-policy unit, each administrative business unit, or each business group unit.

[0154] 14 shows an example of a comparative evaluation screen W7 displayed on the user terminal 3. The comparative evaluation screen W7 comparatively displays evaluation results by policy unit, measure unit, sub-measure unit, task business unit, or business group unit.

[0155] The comparative evaluation screen W7 includes 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, business operations, and the like arbitrarily set via the user terminal 3. When the add button W75 is pressed, it accepts a setting operation for the content to be displayed as the fifth display section, the display format, and the like, and generates the fifth display section based on the setting operation. Although the comparative evaluation screen W7 shows an example of displaying four display sections, the first display section W71 to the fourth display section W74, the number of display sections is not limited, and they can be added, edited, or deleted.

[0156] In Fig. 14, the first display unit W71 displays a list of the 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 for budget increase or reduction. 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 color according to the percentage. The fourth display unit W74 is provided as an interface that allows the user to grasp at a glance the business groups with poor progress status.

[0157] <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 to solve 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.

[0158] 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. The priority issue information can use financial resources classified as the priority budget when setting the budget limit amount. 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.

[0159] <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 administrative 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.

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

[0161] The matching processing unit 27 accepts an input operation of the public recruitment information for the business, including the organization classification and the business classification, via the user terminal 3, and stores it in the storage unit DB. The matching processing unit 27 may accept a selection operation of the business information through the user terminal 3, and generate it based on the business information. The matching processing unit 27 accepts an input operation of the application information for the business, including the organization classification and the business classification, via the request destination terminal 4, and stores it in the storage unit DB.

[0162] 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 a classification of business and operations for which the public offering organization is making a public offering, a classification of business and operations in which the private company making an application specializes, and a classification of business and operations in which the administrative agency making an application wishes to collaborate. The business classification may use the tag name of the tag information, etc.

[0163] The matching processing unit 27 establishes a match for the outsourcing or collaboration of the business corresponding to the public recruitment information and the application information by accepting an input operation for authorizing the application information for the public recruitment information via the user terminal 3 of the recruiting organization. Also, the matching processing unit 27 establishes a match for the outsourcing or collaboration of the business corresponding to the public recruitment information and the application information by accepting an input operation for authorizing the public recruitment information for the application information via the requestee terminal 4 of the applying organization.

[0164] FIG. 15 shows an example of a screen display of a 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 calls for business operations based on the call for business information. The matching screen W8 includes a classification switching unit W81 and a business display unit W82. The classification switching unit W81 accepts a selection operation related to the call for business information, application information, or proposal information, and switches the information displayed as a list in the business display unit W82. The business display units 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 call for business information, application information, or proposal information. In FIG. 15, the business display unit W82 displays the call for business organizations such as local governments that carry out the call for business operations 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 call for business information, the number of proposal information for the call for business information, and the like.

[0165] The proposal information is information generated by accepting an input operation via the requestee terminal 4 of the applicant organization when an input operation permitting application information for the public recruitment information is accepted, and includes a proposal outline such as a specific response plan for the publicly solicited business. The matching processing unit 27 establishes a match between the applicant organization and the applicant organization as a formal request by further accepting an input operation permitting proposal information for the public recruitment information via the user terminal 3 of the applicant organization. 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. [Explanation of symbols]

[0166] 1. Administrative business management system 2 Administrative business management device 21 Business Registration Department 22 Group Registration Department 23 Tag Processing Section 24 Evaluation Section 25 Update section 26 Search processing section 27 Matching processing section 3. User terminal 4. Requested terminal DB storage

Claims

1. It is an administrative business management system, It comprises a business registration department and an evaluation department, The aforementioned business registration department accepts registration of business information relating to business operations established in accordance with laws and regulations. The aforementioned administrative business information has a progress status corresponding to the processing stage of the administrative business, and is associated with business group information based on classification conditions. The evaluation unit evaluates the achievement status of the business group according to the progress status of the business information associated with the business group information, and outputs an evaluation result regarding the progress status of the business group information, in an administrative business management system.

2. The administrative business management system according to Claim 1, wherein the evaluation unit evaluates the achievement status of the business group using an evaluation axis.

3. The administrative business management system according to claim 1, further comprising an update unit that updates the progress status in each processing stage of the administrative business or by the expiration of a period of time.

4. The administrative project management system according to claim 3, wherein the aggregated results of the progress status, indicated by the percentage or total number for each progress status, are reflected in the progress status of the processing stage.

5. The administrative business management system according to claim 1, wherein the evaluation unit outputs an evaluation result regarding the progress status based on the total number of administrative business information associated with the business group information and the number of administrative business information having a predetermined progress status.

6. The aforementioned administrative information includes budget information, including the budget amount and / or revenue amount. The aforementioned business group information includes the total budget and / or total revenue based on the aforementioned budget information, The administrative business management system according to claim 2, wherein the evaluation unit evaluates the progress of the total budget and / or total revenue using the evaluation axis and outputs the evaluation result regarding the progress in the business group information.

7. The invention further comprises a tag processing unit that associates tag information with the business information or the business group information, The administrative business management system according to claim 2, wherein the evaluation unit evaluates the achievement status of the business group using the distribution status of the tag information as the evaluation axis and outputs an evaluation result regarding the distribution status of the tag information in the business group information.

8. The administrative business management system according to claim 7, wherein the tag processing unit outputs a classification result of the tag information related to the administrative business based on the business overview included in the administrative business information.

9. The aforementioned tag information includes organizational tags and business tags. The administrative business management system according to claim 7, comprising a search processing unit that acquires administrative business information with different organizational tags but with common business tags.

10. The aforementioned tag information has a granularity level that includes policies, measures, and administrative projects. The aforementioned evaluation axis is progress, status, achievement, or distribution, The administrative project management system according to claim 7, wherein the evaluation unit evaluates the achievement status of the project group using the progress status, progress, achievement status, or distribution status as evaluation axes, and outputs the evaluation results for the policy unit, the measure unit, and the administrative project unit, respectively.

11. A method of managing administrative projects, A process for accepting registration of administrative information relating to administrative affairs established in accordance with laws and regulations, wherein the administrative information has a progress status corresponding to the processing stage of the administrative affairs and is associated with business group information based on classification conditions, An administrative business management method comprising the steps of: evaluating the achievement status of the business group according to the progress status of the business information associated with the business group information, and outputting the evaluation result regarding the progress status of the business group information, performed by a computer.

12. It is an administrative project management program, The business registration department and the evaluation department will function using computers. The aforementioned business registration department accepts registration of business information relating to business operations established in accordance with laws and regulations. The aforementioned administrative business information has a progress status corresponding to the processing stage of the administrative business, and is associated with business group information based on classification conditions. The evaluation unit is an administrative project management program that evaluates the achievement status of the project group according to the progress status of the administrative project information associated with the project group information, and outputs an evaluation result regarding the progress status of the project group information.

Images