Administrative management system, administrative management method and computer program

Abstract

To provide a technique for efficiently promoting administrative activities in administrative organizations.SOLUTION: An administrative management system for executing object-oriented workflow management: stores administrative data having a plurality of types of data items and registered for every administrative object; creates an issue associated with each administrative object based on a specified topic and administrative object; and determines a processing state of a workflow in the topic using a processing state relating to the issue.SELECTED DRAWING: Figure 1

Description

[Technical field]

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

[0002] 2. Description of the Related Art Information processing techniques are known for improving the efficiency of administrative activities in administrative organizations, including local governments.

[0003] Patent Document 1 discloses technology that aims to resolve the problem of local government financial planning being conducted from a macro perspective, while budget assessments for individual administrative tasks and projects are conducted from a micro perspective, and that in order to resolve this issue, the creation of revenue and expenditure plans for individual administrative tasks and projects is made into rules, made more detailed, and digitalized, and by linking the financial plan for the local government as a whole with the management and evaluation of administrative tasks and projects, it maintains consistency between individual plans and overall strategies, and enables long-term financial estimates based on project accumulation. [Prior art documents] [Patent documents]

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

[0005] The prior art has achieved simplification of the processes related to budget assessment and administrative reform planning, but it is unable to efficiently promote administrative activities in administrative organizations.

[0006] In view of the above-mentioned problems, an object of the present invention is to provide a technique for efficiently promoting administrative activities in an administrative organization. [Means for solving the problem]

[0007] [1] An administrative management system that performs object-oriented workflow management, storing administrative data having a plurality of types of data items and registered for each administrative object; An administrative management system that creates issues associated with individual administrative objects based on a specified topic and administrative object, and determines the processing status of a workflow in the topic using the processing status related to the issue. [2] storing an administrative object group which is a collection of the administrative data; Accepts the designation of administrative object groups to be placed in the workflow and the workflow person in charge, The administrative management system described in [1] creates an issue group, which is a collection of multiple issues corresponding to each of all administrative objects included in a specified administrative object group, based on the specified administrative object group, and assigns multiple issues belonging to the issue group to a person in charge of a specified workflow. [3] Accepts the designation of administrative objects to be included in the workflow and the person in charge of each stage of the workflow, An administrative management system as described in [1] or [2], in which an issue corresponding to a specified administrative object is assigned to a person in charge of each stage, and when a person in charge of a certain stage completes the issue, the workflow progresses to the next stage. [4] An administrative management system described in any of [1] to [3], in which viewing permissions for at least some of the data items of the administrative data and at least some of the data items of the issues are set to different ranges. [5] A user group includes some or all users belonging to the same department, An administrative management system described in any of [1] to [4], wherein viewing permissions are set on a user group basis for at least some of the data items of the administrative data and / or at least some of the data items of the issues. [6] The administrative data is managed by version, and viewing permissions are set for at least some data items of the administrative data for each version; One or more message threads are associated with each of the issues; An administrative management system described in any of [1] to [5], wherein the message thread or a message within the message thread is set with a version of the administrative data in question, and viewing rights are set according to the viewing rights for each version of the administrative data. [7] Data items to be input corresponding to the topic are defined; An administrative management system according to any one of [1] to [6], wherein an input field corresponding to the defined data item is linked to the display screen of the issue. [8] one or more message threads are associated with each of the issues; The administrative management system according to any one of [1] to [7], wherein a mention can be set to a specific user or user group in the message thread or in a message within the message thread. [9] one or more message threads are associated with each of the issues; A posting purpose is added to the message thread or a message within the message thread; The administrative management system described in [2] or any of [3] to [8] quoting [2], wherein the issues in the issue group are aggregated based on any one or more types of posting purpose.

[10] one or more message threads are associated with each of the issues; A reference is added to the message thread or to a message within the message thread; The administrative management system according to any one of [1] to [9], wherein the target of the indication includes a data item or an attachment of the administrative object.

[11] The administrative data may be associated with corresponding administrative data; An administrative management system described in any of [1] to

[10] , wherein the administrative data from previous years referenced when registering new administrative data includes identification information of the new administrative data.

[0008] The invention of [1] makes it possible to manage workflows based on issues linked to administrative objects, thereby efficiently promoting administrative activities.

[0009] The invention of [2] makes it possible to manage the workflow for multiple administrative objects, thereby enabling administrative activities to be promoted efficiently.

[0010] The invention of [3] makes it possible to manage workflows based on issues linked to administrative objects, thereby efficiently promoting administrative activities.

[0011] [4] The invention relates to an efficient promotion of administrative activities while flexibly adjusting the scope of disclosure, for example by disclosing issues to decision makers while keeping documents under adjustment confidential.

[0012] [5] The invention of the present invention makes it possible to efficiently promote administrative activities, for example, when an issue assigned to the head of the original department is processed by the person in charge of the original department.

[0013] The invention related to [6] makes it possible to efficiently promote administrative activities while flexibly adjusting the scope of disclosure.

[0014] [7] The invention relates to efficient administrative activities using issues.

[0015] [8] The invention relates to making it possible to efficiently promote administrative activities, including users outside the workflow.

[0016] The invention of [9] makes it possible to determine the progress of a workflow based on communication within an issue.

[0017]

[10] The invention relates to efficient administrative activities using issues.

[0018]

[11] The invention makes it possible to efficiently promote administrative activities while maintaining relationships with administrative data from previous years, for example, regarding continuing or merged administrative projects, or administrative projects that have been commercialized as administrative issues. Effect of the Invention

[0019] According to the present invention, it is possible to provide a technique for efficiently promoting administrative activities in an administrative organization. [Brief description of the drawings]

[0020] [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] 4 shows an example of a data configuration according to the present embodiment. [Figure 4] 13 is a screen display example of an office business group registration screen according to the embodiment. [Diagram 5] 4 is a process flowchart of a workflow according to the present embodiment. [Figure 6] 13 shows an example of a workflow start screen according to the present embodiment. [Figure 7] 1 shows an example of the progress of a workflow according to this embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0021] The administrative management system, administrative management method, and administrative management 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.

[0022] In this embodiment, the configuration, operation, etc. of the administrative 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.

[0023] <1.1. Definitions of terms, etc.1> The definitions of terms and phrases used in this specification are as follows: An administrative organization is an organization that manages administration, including government offices, ministries, and public organizations of the country and local governments, and in this embodiment, a local government is taken as an example. The administrative management system according to the present invention is used in administrative organizations to operate and manage administrative activities. The policy system is a task system divided into three layers: policy, policy, and business. In this embodiment, the case where business is managed using this policy system is illustrated, but business may be managed by dividing into four or more layers, for example, by providing a layer of sub-policies between policies and business. A policy is a large set of administrative activities aimed at achieving basic guidelines for addressing specific administrative issues, and indicates the direction and objectives of urban development in the administrative division in which it is established (cities, towns, villages, etc.). A policy is a set of administrative activities aimed at achieving a specific policy based on the basic principles of the policy, and indicates the measures and measures for realizing the policy. Tasks and projects are administrative procedures and projects carried out by each bureau in an administrative division based on its budget.

[0024] An administrative object refers to an object to be handled in administrative activities. In this embodiment, the administrative objects are individual business projects, responses, and issues. A reply refers to a reply in a plenary session or a committee prepared by an executive body such as an administrative agency in response to a question from a member of parliament. The issues are those collected during the planning, execution and evaluation stages of administrative projects, as well as by assemblies and committees, and serve as the basis for formulating administrative issues for the next term and beyond. Other than that, for example, policies and the like may also be managed as administrative objects.

[0025] <1.2. Overview of administrative activities> An example of the flow of administrative activities will be explained. Tasks and projects: First, in the planning stage, plans for tasks and projects to be implemented in the next planned execution fiscal year (for example, the following fiscal year) are prepared. Next, in the budget compilation stage, budget requests for tasks and projects to be implemented in the next planned execution fiscal year are prepared, the budget requests are assessed, a budget proposal is prepared, and the proposal is submitted to the assembly. Then, in the execution fiscal year, in the execution stage, the budget is executed for tasks and projects approved by the assembly. In the evaluation stage, an administrative evaluation report is prepared for the tasks and projects that have been executed. Answers: Record the details of questions and general inquiries at plenary sessions and committees as notified, and enter and manage the answers to the notified questions, to prepare answers to plenary sessions and committee responses, etc. Issues: Issues collected during the planning, execution, and evaluation stages of administrative projects and by the assembly, committees, etc. will be evaluated from time to time, and new administrative projects that address the issues will be registered at the planning stage for the next planned execution year and onwards, and perspectives on the issues will be incorporated into existing administrative projects.

[0026] <1.3. Definitions of terms, etc.2> A topic indicates a stepwise division of administrative activities carried out with an administrative object as the object. One or more topics may be defined for each type of administrative object. In this embodiment, for example, when an administrative business is the object, multiple divisions arranged chronologically, such as "plan", "budget compilation>request", "budget compilation>assessment", "budget compilation>informal notice", "budget compilation>resolution", "budget execution", "settlement", and "administrative evaluation", are defined as topics. In addition, when an answer is the object, a topic such as "answer management" for creating an answer to a question is defined, and when an issue is the object, a topic such as "issue management" for accumulating and managing collected issues and sublimating them into an issue is defined. The above is an example, and a division different from these, an abstract division, a subdivided division, etc. may be defined. In addition, the division of topics may be performed by hierarchizing the topics in multiple layers. For example, instead of the topic "Budget preparation > ____", categories such as "Initial budget preparation (hereinafter referred to as "initial") > ____" and "Supplementary budget preparation (hereinafter referred to as "supplementary") > ____" may be defined, and subtopics of "Initial > ____" and "Supplementary budget preparation (hereinafter referred to as "supplementary") > ____" may be defined in a layer under "Budget preparation". Also, multiple categories arranged chronologically may be defined as topics in the lower layers. For example, categories such as "request", "assessment", "unofficial notice", and "resolution" may be defined in a layer under "Budget preparation".

[0027] An issue refers to a subject of administrative activities occurring with respect to each administrative object. An issue is associated with an individual or a group of administrative objects and assigned to a specific person in charge. In this embodiment, an issue is raised with respect to an administrative object of a specific topic or a group of administrative objects belonging to a specific topic.

[0028] A workflow means a repeatable flow of administrative activities. In this embodiment, the workflow includes multiple stages WS that are executed to achieve a certain purpose, and progresses by completing issues assigned to the person in charge at each stage WSn.

[0029] A workflow supports the progress of administrative activities for administrative objects, but may be intended to transition an administrative object to a topic of the next stage, or to make it possible to transition. For example, a workflow for a "planning" topic is the former, and by completing this, it is possible to transition to the next "budget compilation" topic. For example, a workflow for a "budget compilation > resolution" topic is the latter, and an administrative task that has completed the workflow can transition to the "execution" topic when the planned execution year arrives. Alternatively, a workflow may be intended to carry out administrative activities that are carried out repeatedly in a specific topic. For example, a workflow for an "execution" topic includes stages WS such as application to approval, and may be carried out once or multiple times for each administrative task during the budget execution period.

[0030] <2.1. System configuration> Fig. 1 shows a system configuration diagram of an administrative management system 1. As shown in Fig. 1, the administrative management system 1 comprises an administrative management device 2, a user terminal 3, and a database DB, and each component is connected to a communication network NW. For example, the communication network NW includes a comprehensive administrative network (LGWAN: Local Government Wide Area Network), and the administrative management device 2 and the database DB, and the administrative management device 2 and the user terminal 3 are connected via the comprehensive administrative network.

[0031] The administrative management system 1 (administrative management device 2) provides a platform for operating and managing administrative activities related to administrative objects such as administrative projects, etc. The administrative management device 2 comprises, as functional components, an administrative object management unit 21, an administrative object group management unit 22, an issue management unit 23, an issue group management unit 24, and a workflow management unit 25.

[0032] The user terminal 3 is a terminal device used by a user who belongs to an administrative organization. A plurality of user terminals 3 are installed at least within the administrative organization.

[0033] In this embodiment, the users include special officials (such as chiefs) in administrative organizations, users of the secretariat department such as the finance department, section chiefs, department heads, civil engineering departments (bureaus and sections) and agriculture, forestry and fisheries departments (bureaus and sections), and users and managers of original bureaus and original sections (section chiefs, department heads, etc.). For example, original section users perform tasks such as creating project forms such as business plans, creating budget requests, executing budgets, and creating administrative evaluation reports. Secretariat users perform tasks such as requesting original section users to create budget requests and evaluating budget requests. Section chiefs and department heads and special officials perform tasks such as checking deliverables by users, selecting key projects based on plans, prioritizing, and assessing budget requests approved by finance section users. The administrative management system 1 provides each user with a predetermined operating authority, and controls the permission and restriction of predetermined functions according to the operating authority. In particular, a user who performs processing at a certain stage of the workflow is called a person in charge.

[0034] <2.2. Hardware configuration> Fig. 2(a) shows a hardware configuration diagram of the administrative management device 2. The administrative 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 management device 2 can use a computer device such as a server or a personal computer. Note that the administrative management device 2 may be configured with multiple computer devices, and is not limited to the configuration shown in Fig. 2(a) as long as the above-mentioned functional components (21-25) 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 management device 2 by executing an administrative management program, an OS (Operating System), and other applications. The storage unit 202 is configured with one or more memories such as an HDD (Hard Disk Drive), an SSD (Solid State Drive), a flash memory, and a RAM (Random Access Memory), and stores the administrative 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 and the database DB. The control unit 201 executes the administrative management program to cause the computer to function as the administrative management device 2 and execute the administrative management method.

[0036] In the illustrated example, the database DB is a database server accessible via a communication network NW including LGWAN, etc., but it may also be realized using, for example, a control unit 201 and a memory unit 202 that constitute the administrative management device 2, or it may be connected to the administrative management device 2 via a LAN, etc.

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

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

[0039] <2.3.Database> The database DB will store user master data in advance, as well as previous years' administrative and business information (administrative data), business group information, issue information, issue group information, workflow information, as well as response information (administrative data) and issue information (administrative data).

[0040] The user master stores user information within an administrative organization. The user information includes the user's identification information (user ID), name, department (division, section, etc.), etc. A user group, which is a collection of one or more users, may be defined. The user group information may be predefined, for example, by the user group's identification information (user group ID) and the identification information of users belonging to the user group, or users having a common attribute (department) may be treated as a user group. Users to be included in a predefined user group may be arbitrarily selected, or may be selectable from user groups having a common attribute. A user group is specified by an arbitrarily set group name or an attribute name that represents the characteristics of the group.

[0041] The business and project information is administrative data related to each business and project, and is registered for each planned execution year. In this embodiment, the business and project information includes basic information related to the business and project (basic business information), administrative goal information, budget information, and execution information related to the business and project. Basic information on business operations and projects (basic business information on business operations) is information on the contents of business operations and projects, and includes identification information (business operation ID) of the basic information (i.e., business operation information), planned execution year, identification information (business operation ID) of related administrative data described below, status, and information on multiple data items related to the business report of the project. Data items of basic information (basic business information on business operations) include various information related to the project, such as project number, project name, responsible department (department, section, etc.), project start year, project end (planned) year, accounting classification, legal basis, main policy / measure to which the business operation belongs, project purpose, project overview, implementation method, etc.

[0042] The status of basic information (basic information on business operations) indicates the stage of the business in administrative activities, and has at least a status corresponding to the topic. For example, statuses such as "Plan", "Budget preparation > Request", "Budget preparation > Assessment", "Budget preparation > Preliminary announcement", "Budget preparation > Resolution", "Execution", and "Administrative evaluation" are given. Here, for businesses that have received a zero assessment (not included) at the "Budget preparation > Preliminary announcement" stage, the status remains "Budget preparation > Preliminary announcement". "Budget preparation > Assessment" classifies businesses that have not yet been assessed or are being assessed, and businesses that have been put on hold as a result of assessment, while "Budget preparation > Request" classifies businesses that are at the budget request stage and businesses that have been put on hold for which a request for revival has been made. These statuses are just examples, and the stages of each status can be divided arbitrarily, and the number of stages is not limited to these. In addition to or instead of the staged statuses corresponding to the topics, a status related to the assessment result, such as included or not included, or a status related to the evaluation result of the business operations, such as continued or discontinued, may be given.

[0043] The administrative goal information defines the KPIs for achieving each task or project, i.e., the tasks to be achieved during the execution period of the task or project. Multiple pieces of administrative goal information may be set for each task or project, in stages. The administrative goal information has identification information for the administrative goal (administrative goal ID), as well as data items such as the content of the administrative goal and the deadline for achieving the administrative goal. In addition to the deadline for achievement, it may also have a reminder timing.

[0044] The budget information includes initial budget information indicating an initial budget for a certain task or project, and supplementary budget information indicating a supplementary budget. The initial budget information includes identification information for the initial budget (initial budget ID), identification information for related administrative data (business ID), and multiple data items related to the initial budget. The data items of the initial budget information include, for example, an outline of the initial budget, items such as subdivision items related to the budget, and the budget request amount. The supplementary budget information includes identification information of the supplementary budget (supplementary budget ID), monthly, identification information of related administrative data (initial budget ID), and multiple data items related to the supplementary budget. The data items of the supplementary budget information include, for example, an overview of the supplementary budget (purpose, reason, etc.), items such as subdivision items related to the budget, and the budget request amount. Note that the items related to the initial budget and the supplementary budget are just examples, and items of any granularity such as sections, subsections, etc. may be included. For example, these items may be stored in an item master, and may be referenced in the business information by identification information (item ID) in the item master.

[0045] Execution information is information that is registered from time to time for budget execution during the execution period. Execution information includes execution identification information (Execution ID), identification information for the task / project that performs the budget execution (Project ID), and data items such as execution date, item, and amount of execution. Sections, subsections, etc. may be added to the item at the stage of registering execution information.

[0046] The assignment information is administrative data related to each assignment. In this embodiment, the assignment information includes assignment identification information (assignment ID), related administrative data identification information (task ID), and multiple data items related to the assignment. Data items of the assignment information include, for example, the assignment name, assignment content, relevant policy, measure, business project, supervising organization, and assignment creator (user ID).

[0047] The reply information is administrative data related to each reply. In this embodiment, the reply information includes reply identification information (reply ID), related administrative data identification information (issue ID), and multiple data items related to the reply. Data items for reply information related to plenary sessions include, for example, the name of the assembly, the date of the plenary session, the name of the assembly member who asked the question, the party that asked the question, the type of question (general question / urgent question), the content of the question, the category of the replyer (head of the local assembly, department head, section head, etc.), the department responsible for preparing the reply (department, section office, etc. (consultation destination)), the content of the reply, and the person who prepared the reply (user ID), etc.

[0048] <2.4. Example of data structure based on related administrative data> FIG. 3 is a diagram showing an example of related administrative data. The related administrative data is administrative data related to certain administrative data, and one or more may be set. The related administrative data is, for example, past year business information when a business is continued, another business information when a business is integrated, issue information that is the source of the business, and answer information that is the source of the administrative issue. In this embodiment, each administrative data is associated with each other by a reference structure as shown in FIG. 3. When a business is continued or integrated, the newly registered business information and the corresponding business information are associated with each other by the related administrative data. The identification information of the related administrative data of the business basic information (execution year: 2022) is blank at the stage of registration. When new business information that continues the business is registered, the identification information (business ID) of the new business information is input. In the illustrated example, the business basic information (execution year: 2023) (business ID: 2222) is assigned as the related administrative data of the business basic information (execution year: 2022). In addition, when multiple projects from previous years are integrated, the same identification information for the new project information (project ID) will be entered into the multiple project information for the previous years. When integrating projects, the project information for the current year associated with the project information for the current year for the main project and the project to be integrated may be registered, and then the project information for the integrated project may be associated as related administrative data for the project information for the main project for the current year. When an administrative issue is turned into a business, the newly registered business information is associated with the issue information accumulated in the immediately preceding period, etc., through related administrative data. In the illustrated example, the related administrative data in the issue information (implementation year: 2021) is the business (business ID: 1111) that corresponds to the issue or has been developed from the issue. When accumulating administrative issues from the contents of responses, the newly registered issue information and the accumulated response information are associated with related administrative data. In the illustrated example, the related administrative data in the response information (execution year: 2021) is the issue (issue ID: 9999) that was elevated from the response. The relevant administrative data for the initial budget information (implementation year: 2023) is the basic information on administrative operations related to the budget (implementation year: 2023) (administrative operations ID: 2222). The related administrative data in the supplementary budget information is, for example, the initial budget information related to the supplementary budget (initial budget ID: 3333). The related administrative data in the supplementary budget information may be, for example, the immediately preceding supplementary budget. In the illustrated example, when new administrative data is registered, matching is achieved by assigning identification information of the new administrative data to the previously registered administrative data, but matching may also be achieved by assigning identification information of the previously registered administrative data to the newly registered administrative data.

[0049] <3.1. Registration of administrative object groups> <3.1.1. Registration of administrative objects (administrative data)> The registration of an administrative object group will be described with reference to FIG. The administrative object management unit 21 registers administrative data related to administrative objects. For example, the administrative object management unit 21 stores various administrative data in the database DB and edits existing administrative data based on a request to register new administrative data such as business information, issue information, and reply information. In addition, the administrative object management unit 21 uses data items included in the issue information stored in the database DB to register business information in which corresponding data items have been input (preset), and uses data items included in the reply information stored in the database DB to register issue information in which corresponding data items have been input (preset).

[0050] <3.1.2.Status of administrative objects> The administrative object management unit 21 sets the status of an administrative object. In the above example, a status is assigned to business information, but a status may also be assigned to answer information or issue information depending on the stage or state of the topic (pre-approval, under approval, etc.). The administrative object management unit 21 changes the status of an administrative object, for example, when the workflow of a certain topic is completed. Instead of or in addition to the completion of the workflow, the status may be changed depending on the planned execution year and actual date and time of the administrative object.

[0051] <3.1.3. Authority of administrative objects> Furthermore, the administrative object management unit 21 manages the authority for administrative objects. The authority is, for example, the authority to view administrative data, the authority to edit and view, etc. The authority may be for at least some data items of the administrative data, or may be for all data items. The authority is set for a user group or an individual user. The authority for administrative objects may be granted to a user other than the user designated as the person in charge of the workflow. In this embodiment, the authority to view and the authority to edit and view administrative objects are set according to the department to which the user belongs.

[0052] The viewing authority and / or editing authority may be changed depending on one or more of the topics to which the administrative object belongs and the workflow stages WS. For example, in the "Budget Preparation > Request" topic, users from the original department can input data items for the task, but when the workflow stage progresses after submitting to a superior, or for the task that has progressed to the "Budget Preparation > Assessment" topic, the editing authority is invalidated. Such changes in authority may differ depending on the department or position. For example, even in the "Budget Preparation > Assessment" topic, users from the Secretariat department may be able to edit the task.

[0053] <3.1.4. Version of administrative objects> When administrative data is updated, the administrative object management unit 21 records the history and performs version management of the administrative data. In this embodiment, the person in charge of each stage in the workflow registers a version for the administrative data. When registering a version of administrative data, a user group or user who has the authority to view the original version of the administrative data is preset, and any user group or individual user can be added or deleted as necessary. The administrative object management unit 21 may automatically register a version as the workflow progresses. Note that the version may be registered even when it does not necessarily involve editing of the administrative data. Also, instead of or in addition to registering according to the workflow stage, the administrative object management unit 21 may register a version when editing of the administrative data is performed and / or when the topic of the administrative data is changed. For example, when the workflow of updating the administrative data and approving it is completed, the administrative object management unit 21 stores a new version of the administrative data. For example, the administrative object management unit 21 of a certain topic may manage the authority for each version of the administrative object.

[0054] <3.1.5. Administrative Object Group> The administrative object group management unit 22 registers administrative object groups, which are collections of multiple administrative objects. The administrative object group management unit 22 is used when multiple administrative objects are put together into a workflow. The administrative object group management unit 22 can group administrative objects when they have at least one or more of the following items in common: (1) Fiscal year in which execution is planned (2) Type of administrative object (business, response, issue, etc.) (3) Budget type (initial budget, supplementary budget) (4) Topic to which the administrative object belongs (status in business information) In this embodiment, the administrative object group management unit 22 groups all or selected administrative objects among the administrative objects having all of (1) to (4) in common into one administrative object group, and stores the administrative object group information in the database DB. The selected administrative object may be an administrative object selected arbitrarily by the user, or may be an administrative object specified by a specific data item (e.g., a policy or a responsible department) arbitrarily designated by the user.

[0055] The administrative object group information includes identification information of the administrative object group (administrative object group ID), the group name, the planned execution year, the topic, and identification information of multiple administrative objects belonging to the group.

[0056] <3.1.6.Administrative object group registration screen> 4 shows an example of the screen display of the administrative object group registration screen W4 displayed on the display unit 905 of the user terminal 3. The administrative object group registration screen W4 has an input field W41, an administrative object display field W42 within the group, a search field W43, a search result list W44, and a save button W45. A user such as an original bureau or original department inputs a group name of an administrative object (a business / task group name in the illustrated example) into the input field W41 via the input unit 904 of the user terminal 3, and also specifies a topic of the administrative object to be included in the group. In addition, various data items related to business / tasks are input as search conditions into the search field W43, and a search is performed for business / tasks to be included in the group.

[0057] In the search field W43, the planned execution year of the administrative object and keywords for searching topic (status) data items (for example, accounting classification of the business, policy, measure, budget information, and execution information subjects) can be entered, and these can be used to search for administrative objects. The topics that can be specified in the search field W43 are subordinate topics corresponding to the topic specified in the input field W41. The searched administrative objects are displayed in the search result list W44, and can be added to a group by pressing the corresponding add button. In addition, by pressing the details button, information (for example, business forms related to the business) can be displayed on the display unit 905 of the user terminal 3 based on the administrative data. When the save button W45 is pressed, the administrative object group management unit 22 stores the business group information including the group name, topic, and added business entered in the input field W41 in the database DB, and registers the business group. In this embodiment, a topic is set for the administrative object group, but for example, when the workflow starts, the administrative object group may be selected and a topic may be specified. In this embodiment, the registration of administrative business groups, which are groups of administrative businesses, has been described, but administrative objects such as issues and replies can also be organized into groups on the same screen by narrowing down the search by fiscal year or other data items.

[0058] <3.2. Registering an Issue Group> <3.2.1. Registering an issue> The issue management unit 23 registers an issue associated with an administrative object. In this embodiment, the issue management unit 23 registers an issue by storing issue information in a database DB. When an issue is registered, the person in charge is notified that the issue has been registered, and the person in charge checks the content of the issue and performs administrative activities. The issue management unit 23 registers an issue based on a request from a user to create an issue or a request to start a workflow. Note that a user may be able to register an issue as the person in charge.

[0059] Issue information includes issue identification information (issue ID) and, as data items for the issue, identification information for the corresponding administrative object (business ID, response ID, issue ID), issue title and content, one or more responsible persons, issue creator, issue status, deadline, attachments, work items, issue type, and issue group identification information (issue group ID) described below.

[0060] The issue management unit 23 sets the person in charge of an issue in at least one of the following ways. (11) A user or user group selected by the user who creates an issue or initiates a workflow (12) The users and departments set in the administrative data linked to the issue (13) A user (user group) selected according to the attributes (affiliation, position, etc.) selected by the user who creates an issue or starts a workflow When a user group is designated as the person in charge, the issue management unit 23 may assign the leader of the group to the issue, or may assign multiple users belonging to the group to the issue. Alternatively, each administrative object may be linked to an individual user, and a user in the user group designated as the person in charge of the issue, or a user under an individual user (e.g., a supervisor) designated as the person in charge, may be assigned as the person in charge of the issue according to the user linked to the administrative object. Also, the person in charge of an issue may be different from the user who actually performs the work. For example, an individual user (e.g., a manager) may be assigned to an issue as the person in charge, and the work (e.g., inputting data items) may be performed by another user (e.g., a user under the manager) in response to a request in real life or a request (mention) via a thread described later. The issue types include a type with an input form linked to an input form for inputting one or more specific data items, and a type without an input form. In the case of an input form, an input field for any one or more data items is arranged on the display screen of the issue or on an input screen that can be moved from the display screen of the issue, and the user can input data values ​​for the data items through this input field.

[0061] <3.2.2. Issue Status> The issue management unit 23 sets the person in charge of an issue and the issue status. The issue status is, for example, "needs work," "returned," "completed," etc. The issue management unit 23 may change the issue status in response to a completion operation from the issue creator, or may change the issue status when the workflow ends.

[0062] <3.2.3. Issue authority> Furthermore, the issue management unit 23 manages the authority for the issue. The authority is, for example, the authority to view the issue, the authority of the person in charge, etc. The viewing authority may be for at least some of the data items of the issue, or may be for all of the data items. The authority of the person in charge is related to the change of the issue status and the progress of the workflow, such as the approval of the submitted content, the return, etc. A user who is assigned an issue and has the authority of the person in charge activated performs the work requested by the title and content of the issue, the topic of the corresponding administrative object, etc. The work is, for example, inputting the data items, registering the created attachment to the issue, editing (and reattaching) the attachment to the issue, inputting the data items from the linked input form, etc.

[0063] The authority is set for a user group or an individual user. The viewing authority for an issue may be given to a person in charge of the current stage WS of the workflow, a person in charge of another stage, and a user other than the person in charge. In this embodiment, the viewing authority for an issue is set according to the department (user group) to which the user belongs, and the person in charge authority of the issue is transferred between the people in charge of the issue according to the stage WS of the workflow. For example, the first person in charge assigned to the issue is given the person in charge authority, and when the first person completes the issue (for example, submits), the person in charge authority of the first person is invalidated and the person in charge authority (for example, approve / return) is transferred to the person in charge of the next stage WS (the second person in charge). The viewing authority for the administrative object and the issue may be linked, or the viewing authority may be set to a different range. In this embodiment, the viewing authority for the administrative object and the issue is for a different range.

[0064] <3.2.4.Thread> On an issue, at least an independent thread (message thread) can be created for each issue. In this embodiment, a user (including a person in charge) can communicate with other users by messages on a thread regarding administrative activities for a certain administrative object. Messages exchanged on a thread include at least text, and at least one of a mention, a posting purpose, a subject of criticism, a usage authority, and a status is set for the message and / or thread. A mention indicates any user or user group to be notified of the creation of a thread and / or the posting of a message, and one or more of these can be specified. A posting purpose indicates the purpose of creating a thread or posting a message, and one or more can be set. Some or all of the posting purpose may be predefined (e.g., "point out", "return"), or free text may be written. A point out target is a specification of a data item or attachment of an administrative object that is the subject of a thread or message. Usage permissions include the permission to view a thread, the permission to view individual messages, and the permission to post messages. A status indicates the state of communication in a thread (e.g., "in progress", "completed", etc.). A message may also include a reference (reply) to any message.

[0065] In this embodiment, the issue management unit 23 creates a thread in association with an issue based on a request from a user. When creating a thread, the issue management unit 23 accepts settings of the posting purpose for the thread, the setting of the target of criticism, the authority setting, and the mention setting for any user. The posting purpose includes those that are defined in advance and those that are written as text, and one or more posting purposes set in the thread are added as tags. In addition, the issue management unit 23 changes the status of the thread from in progress to completion by a completion operation by the creator of the thread, controls the use of the user based on the authority setting, and accepts the posting of a text message for the thread and any reply setting. When the administrative object management unit 21 manages the version of the administrative object, the issue management unit 23 may further accept settings of the version of the administrative data to be targeted for the thread or the message on the thread, and indicate the version of the administrative object to be targeted by the message in the thread together with the posting purpose of the thread, etc.

[0066] <3.2.5. Thread and message permissions> A thread for which no usage authority has been set is called an open thread, and a thread that can only be used by users with usage authority is called a private thread. An open thread can be used by users who have viewing authority for the corresponding issue. For example, when advancing a workflow stage, a message can be written along with the completion operation of the issue, and messages such as matters to be passed on that were written at the time of the completion operation are posted in the open thread. Private threads can only be used by users who have permission to view the issue and who also have permission to use the thread. Permission to use a private thread is set by the user who created the thread. When the administrative object management unit 21 manages the authority for each version of the administrative object, the issue management unit 23 may further accept the setting of the version of the administrative data to be targeted for the private thread or the message on the private thread, and grant the use authority of the private thread or the message on the private thread to some or all of the users who have the viewing authority for the corresponding version of the administrative object and the issue. When registering a private thread or a message on a private thread linked to a version of administrative data, a user group or user who has the authority for the issue and the administrative data of the version is preset, and any user group or individual user can be deleted as necessary. The issue management unit 23 may automatically register the use authority of the private thread or the message on the private thread according to the authority to the issue and the administrative data of the version, and at this time, the use authority may be granted under an AND condition with other conditions of the private thread.

[0067] <3.2.6. Generation of issue information according to workflow> In this embodiment, the person in charge of an issue is updated for each workflow stage WS, and moves between the people in charge in a so-called Kanban-style Kanban manner. This allows information (comments, etc.) linked to issues in past stages WS to be stored for reference. Meanwhile, new issue information linked to the same administrative object may be generated for each workflow stage WS (each person in charge). In this case, for example, by including identification information and serial numbers of the immediately preceding and / or following issues in the successive issue information in the workflow, or by including them in the workflow information, the chronological relationship and order of the corresponding issues, and information linked to each issue (comments, etc.) are stored for reference.

[0068] <3.2.7. Issue Group> The issue group management unit 24 registers an issue group. In this embodiment, the issue group management unit 24 registers issues corresponding to all administrative objects included in a specified administrative object group in the issue management unit 23, and stores issue group information related to an issue group consisting of these issues in the database DB, thereby registering the issue group. The issue group information includes identification information of the issue group (issue group ID), the group name, and identification information of the corresponding administrative object group (administrative object group ID).

[0069] <3.3. Registering workflow information> The workflow management unit 25 registers workflow information and manages the processing status of the workflow using the processing status of the issues listed in the workflow. The person in charge of processing in the first stage of the workflow is determined according to the method for determining the person in charge of the issue. The workflow management unit 25 sets the person in charge of the second and subsequent stages of the workflow using at least one of the following methods. (21) A user who starts a workflow, or a user or group of users selected by the person in charge of a certain stage WS (22) Users and departments set in administrative data (23) A user or a user group selected according to attributes (affiliation, position, etc.) defined for each stage WS of the workflow When multiple people are specified, the order of the people, that is, the order of the workflow stages WS, is specified. One person in charge may be set for each stage of the workflow (serial), or multiple people may be set for some stages in the workflow (parallel). In that case, the stage may advance when some of the people in charge have given their approval, or when all of the people in charge have given their approval.

[0070] The workflow management unit 25 inserts a stage based on a request from a person in charge. It is preferable that a person in charge with an enabled person in charge authority can insert a stage. For example, a person in charge of a certain stage WSn can designate a person in charge 1 and insert a stage WSn', and request the person in charge of the stage WSn' to perform work or to confirm (approve). The person in charge of the inserted stage WS may be able to insert a further stage WS. A person in charge of a certain stage WS may designate multiple people and request work from multiple people (in parallel) in stage WSn'. When a completion operation (submission or approval) is performed in stage WSn' of the inserted workflow, the issue is handed over to a person in charge of the next stage WSn+1. Here, the issue may be returned to the person in charge of the immediately preceding stage WSn, and the person in charge of the immediately preceding stage WSn may perform a completion operation on the issue, so that the workflow proceeds to the next stage WSn+1. When multiple people in charge are in parallel, multiple people may be set for each issue, and when the immediately preceding person in charge has multiple issues, some or all of them may be distributed and assigned.

[0071] A user who starts a workflow starts the workflow by designating at least the first person in charge. Workflows include workflows defined for each topic and workflows that can be executed at any time. In a workflow defined for each topic, at least two people participate: a person in charge of tasks such as inputting and checking data items (or supervising the input and tasks), and a final approver. There may be one or more intermediate approvers before the final approver, and when a person in charge completes an issue, the issue is assigned to the next intermediate approver. If there are two or more intermediate approvers, the issue is assigned to the next intermediate approver when the previous intermediate approver completes the issue. If there is only one intermediate approver, or when the last intermediate approver completes the issue, the issue is assigned to the final approver. When the final approver completes the issue, a notification is sent to the workflow creator and the issue is assigned.

[0072] At each stage WS of the workflow, processing is performed such as creating a specified administrative object, inputting data items, and confirming (approving) the inputted data items. The workflow management unit 25 may define the processing possible at each stage of the workflow in at least one of the following ways: (31) A process selected by a user who starts a workflow or a person in charge of a certain stage WS (32) Processing selected from the users or user attributes set in the administrative data (for example, the person in charge of the original department inputs data items, and the department manager or division chief approves the data, etc.) (33) Processing defined for a workflow stage WS (for example, input is performed at stage WS1 or stage WS1' inserted at stage WS1, and confirmation is performed at stages WS2 and after) The issue status corresponds to this process, and may be set to, for example, "inputting," "before interim approval," "interim approved," "before final approval," "final approved," or the like.

[0073] A workflow that can be executed at any time is executed by a minimum of two people when a question or inquiry is made. For example, an issue containing the sender's question or inquiry is assigned to the sender and destination users, and the destination user's person in charge authority is enabled. When the destination user (person in charge) completes the issue by writing a response comment, etc., the sender user's person in charge authority for the issue is enabled. If the question or inquiry is resolved, the sender user completes the issue, ending the workflow. If the issue is not resolved, the next step is performed and the destination user's person in charge authority is re-enabled.

[0074] The topic, administrative object, responsible person, and timing may be defined in advance to schedule the start of the workflow. For example, the start date of the workflow may be registered, and when the start date arrives, an issue may be registered in the issue management unit 23 to start the workflow. Also, for example, based on the reminder timing included in the administrative goal information, an issue for administrative goal information registration may be assigned to a responsible person associated with the administrative goal information, and the workflow for administrative goal information registration may be started.

[0075] The workflow management unit 25 determines the processing status of the workflow based on the processing status of the issues placed in the workflow. The processing status of an issue is the issue status of the issue, the person in charge of the issue (workflow stage), etc. Also, the (workflow) processing status of an administrative object group can be determined from the processing status of an issue group. The processing status of an issue group is the result of tallying up the issue status of issues in the issue group, the result of tallying up the workflow stage, the result of tallying up the posting intent attached to a topic or message, etc.

[0076] <4.1. Workflow processing flow> Next, a case where an issue group is placed in a workflow linked to a topic will be described with reference to Fig. 5. First, a user who wishes to start a workflow registers an administrative object group that is to be the target (see S501 in Fig. 5). Then, the user specifies the administrative object group via a workflow registration screen as shown in Fig. 6, and starts the workflow (see S502 in Fig. 5).

[0077] 6(a) shows an example of a screen display of a workflow start screen W6a displayed on the display unit 905 of the user terminal 3. The workflow start screen W6a includes a workflow information input field 6a1 and a start button W6a2. The user inputs, in the workflow information input field 6a1, the workflow name, the administrative object group that is the subject of the workflow (in the illustrated example, the administrative business group), the person in charge of processing at each stage of the workflow, a progress schedule indicating the start date and end date of the workflow, instructions for the person in charge, a message regarding an explanation of the workflow content, etc., and presses the start button W6a1 to start the workflow. In this embodiment, the start date and end date of the workflow are set in the issue information as the deadline for the issue, and the workflow content is set as the content of the issue.

[0078] In this embodiment, the user who registered the workflow designates in advance the person in charge at each stage of the workflow. In the example of Fig. 6, when the workflow is started, issues are assigned to the persons in charge "AAA", "BBB", and "CCC", and the person in charge authority of the person in charge "AAA" is first enabled. Then, when the person in charge "AAA" completes the issue, the person in charge authority of the next person in charge "BBB" is enabled. Then, when the person in charge "BBB" completes the issue, the person in charge authority of the last person in charge "CCC" is enabled. Furthermore, it may be possible to assign the issue to yet another person in charge (inserting a stage) before proceeding to the next stage WS. For example, before person in charge "AAA" completes the issue, another person in charge "DDD" can be specified and the issue can be assigned. At this time, when person in charge "DDD" inserted in the progress of the workflow completes the issue, the person in charge authority of person in charge "BBB" who is the next person in charge of person in charge "AAA" may be enabled, or the person in charge authority of the original person in charge "AAA" may be enabled again. At this time, the handover of work between person in charge "AAA" and "DDD" may be registered as separate workflow information.

[0079] The workflow information includes the workflow identification information (workflow ID), the workflow name, the identification information (administrative object group ID) of the administrative object group that is the target of the workflow (in the illustrated example, the administrative business group), the person in charge, the progress schedule, and a message.

[0080] When a workflow is started, the issue management unit 23 registers an issue for each individual administrative object belonging to the administrative object group associated with the workflow, and the issue group management unit 24 registers an issue group consisting of these issues (see S503 in FIG. 5), and the issue management unit 23 assigns the registered issues to persons in charge 1 to N (see S504 in FIG. 5). The persons in charge can display a list of the issues assigned to them, and can also display issue information that can refer to data items related to the associated administrative object. Note that users can view issues that are not assigned to them and post messages, etc., depending on their issue authority settings.

[0081] The workflow includes multiple stages WSn. First, stage WS1 is started (see S505 and S506 in FIG. 5), and the issue management unit 23 grants person in charge authority to the person in charge 1. The person in charge 1 executes the work and performs a completion operation on the issue (S507 in FIG. 5). The issue management unit 23 can determine the type of issue according to the topic of the workflow (in the embodiment, the topic of the administrative object group associated with the workflow), and when a workflow of a specific topic is started, it can register an issue to which an input form for a predetermined one or more data items is linked and assign it to a person in charge. In this case, the person in charge can display the issue information to which the input form is linked.

[0082] Here, if a completion operation by another person in charge is required, the process waits for the completion operation by the other person in charge. When the completion operations by all the necessary persons have been performed (see S508 in FIG. 5), stage WS1 (see S509 in FIG. 5) is completed. If all stages N included in the workflow have not been completed (see S510 in FIG. 5), the next stage is executed (see S511 in FIG. 5). When all stages N included in the workflow have been completed (see S510 in FIG. 6), the workflow is terminated (see S512 in FIG. 5).

[0083] FIG. 6(b) is an example of a screen display of the business task group list screen. In the business task group list screen W6b, the processing status of the workflow, which is tallied by the workflow management unit 25, is displayed. In the illustrated example, when the workflow has four stages, the stage at which each issue in the business task group has progressed is tallied and displayed. In the illustrated example (group name: 2023 budget preparation), the issue group contains 17 issues, of which 15 have progressed to the first stage and 2 have progressed to the second stage. Note that here, the workflow management unit 25 tallies the number of issues by stage, but for example, any data item, such as the budget amount of the administrative project corresponding to the issue, may be tallied and displayed by stage.

[0084] <4.2. Example of workflow progress> A specific example of a workflow will be described with reference to Fig. 7. Fig. 7 shows an example of the progress of a workflow related to a budget compilation topic. First, the person in charge of the secretariat department starts a workflow for the task and business group in which the budget compilation topic is set, with the original section manager, the finance section manager A, the finance section manager B, and the head of the local government as the task and business managers. As a result, issues are assigned to each task and business manager, and a request is made to the original section manager to create a budget request document for each task and business belonging to the task and business group (see FIG. 7WS1). The original section manager, who has been requested to create a budget request document, interrupts multiple original section managers, including the original section manager A, as the task and business managers, and divides and assigns the issues belonging to the issue group (see FIG. 7WS2). The division of issues is automatically assigned by the issue management unit 23, for example, by referring to the information of the person in charge (the person responsible for creating the issue) registered in the task and business information. The multiple original section managers, including the original section manager A, to whom the issues are assigned, create a budget request document by inputting predetermined data items related to the task and business information, and submit the issues related to the task and business information for which the budget request document has been created in order for the original section manager to assess them (see FIG. 7WS3).

[0085] The original section manager, upon receiving assignments for all issues included in the issue group from multiple original section staff members, including original section staff member A, and completing the assessment, performs a budget request submission operation. As a result, the authority of the person in charge for all issues included in the issue group is transferred to finance section staff member A, who was set as the person in charge beforehand, and a project assessment is performed (see Figure 7WS4). Upon completing the project request assessment, finance section staff member A performs a request to create a project budget proposal. As a result, the authority of the person in charge for all issues included in the issue group is transferred to finance section staff member B, who was set as the person in charge beforehand, and a request to create a project budget proposal is made (see Figure 7WS5). Upon completing the creation of the project budget proposal, finance section staff member B performs a request to create a project budget proposal. As a result, the authority of the person in charge for all issues included in the issue group is transferred to the head of the local government, who was set as the person in charge beforehand, and a request to assess the budget proposal is made (see Figure 7WS6). Upon completing the assessment of the budget proposal, the head of the local government performs a budget proposal assessment completion operation. As a result, the workflow ends, and a notification is sent to the person in charge of the secretariat department who started the workflow. [Explanation of symbols]

[0086] 1. Administrative Management System 2 Administrative management device 21 Administrative Object Management Department 22 Administrative Objects Group Management Department 23 Issue Management Department 24 Issue Group Management Department 25 Workflow Management Department 3. User terminal

Claims

1. An administrative management system that performs object-oriented workflow management, storing administrative data having a plurality of types of data items and registered for each administrative object; An administrative management system that creates issues associated with individual administrative objects based on a specified topic and administrative object, and determines the processing status of a workflow in the topic using the processing status related to the issue.

2. storing an administrative object group which is a collection of said administrative data; Accepts the designation of administrative object groups to be placed in the workflow and the workflow person in charge, The administrative management system described in claim 1, which creates an issue group which is a collection of multiple issues corresponding to each of all administrative objects included in a specified administrative object group based on the specified administrative object group, and assigns the multiple issues belonging to the issue group to a person in charge of a specified workflow.

3. Accepts the designation of administrative objects to be placed in the workflow and the person in charge of each stage of the workflow, 2. An administrative management system as described in claim 1, wherein an issue corresponding to a specified administrative object is assigned to a person in charge of each stage, and when a person in charge of a certain stage performs an operation to complete the issue, the workflow progresses to the next stage.

4. The administrative management system according to claim 1 , wherein viewing rights to different ranges are set for at least some of the data items of the administrative data and at least some of the data items of the issues.

5. A user group includes some or all users who belong to the same department. The administrative management system according to claim 1 , wherein viewing rights are set on a user group basis for at least some of the data items of the administrative data and / or at least some of the data items of the issues.

6. The administrative data is managed by version management, and a viewing authority is set for each version of at least some data items of the administrative data; One or more message threads are associated with each of the issues; The administrative management system of claim 1, wherein the message thread or a message within the message thread is set with a version of the administrative data in question, and viewing rights are set according to the viewing rights for each version of the administrative data.

7. A data item to be input corresponding to the topic is defined; The administrative management system according to claim 1 , wherein input fields corresponding to the defined data items are linked to the issue display screen.

8. One or more message threads are associated with each of the issues; The administrative management system according to claim 1 , wherein a mention can be set for a specific user or user group in the message thread or in a message within the message thread.

9. One or more message threads are associated with each of the issues; A posting purpose is added to the message thread or a message within the message thread; The administrative management system according to claim 2 , wherein the issues in the issue group are tallied based on any one or more types of the posting purpose.

10. One or more message threads are associated with each of the issues; A reference is added to the message thread or to a message within the message thread; The administrative management system according to claim 1 , wherein the indication target includes a data item or an attachment of the administrative object.

11. An administrative management method for performing object-oriented workflow management, comprising: A computer that stores administrative data having a plurality of types of data items and that is registered for each administrative object, creating issues associated with each administrative object based on the specified topic and administrative object; and determining a processing status of the workflow in the topic using the processing status regarding the issue.

12. A computer program that causes a computer to execute the administrative management method according to claim 11.

Images