Administrative management system, administrative management method, and computer program

Abstract

The objective of the present invention is to provide a technique for efficiently advancing administrative activities in an administrative organization. This administrative management system for managing administrative data stores administrative data including a plurality of types of data items, and an attribute-specific data item set, which is a set of data items set using user attributes, and / or a step-specific data item set, which is a set of data items set using administrative activity steps, and determines data items to be subjected to display processing, on the basis of the attribute-specific data item set corresponding to an attribute of a user making a display request, and / or the step-specific data item set corresponding to the step of the administrative activity of the user making the display request.

Description

Administrative management system, administrative management method, and computer program

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

[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 a technology that aims to solve the problem of local government financial planning being carried out from a macro perspective, while budget assessments for individual administrative projects are carried out from a micro perspective, and that the two are not linked. The technology makes it possible to maintain consistency between individual plans and overall strategies by making the creation of revenue and expenditure plans for individual administrative projects rules, making them more detailed, and implementing IT, and by linking the financial planning of the local government as a whole with the management and evaluation of administrative projects, thereby enabling long-term financial estimates based on project accumulation.

[0004] Japanese Patent Application Laid-Open No. 2005-293321

[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 technology for efficiently promoting administrative activities in administrative organizations.

[0007] [1] An administrative management system that manages administrative data, storing administrative data having multiple types of data items, and attribute-based data item sets that are sets of data items set using user attributes, and / or stage-based data item sets that are sets of data items set using stages of administrative activities, and determining the data items to be displayed based on the attribute-based data item sets that correspond to the attributes of the user who has made a display request, and / or the stage-based data item sets that correspond to the stages in the administrative activities of the user who has made the display request. [2] The administrative management system described in [1], storing linkages of corresponding administrative data at different points in time, matching the data items of each administrative data, arranging corresponding data items included in the administrative data, and displaying differences in corresponding data items. [3] The administrative management system according to [1] or [2], wherein the administrative data includes data items related to system items defined as master data in a multi-level tree structure, and aggregates the number of administrative data items, the number of breakdown items included in the administrative data, or one or more integrable data items linked to the administrative data based on the system items and aggregation axes including at least the execution year and budget type. [4] The administrative management system according to any of [1] to [3], wherein a form-specific data item set is stored, which is a collection of the data items required for each form type, and displays a form in which the data items selected based on the form-specific data item set corresponding to a specified form type are laid out. [5] The administrative management system according to any of [1] to [4], wherein for each administrative data item, at the budget compilation stage, budget item system items related to sub-budget items and breakdown items to which budget information is associated are registered, and at the execution stage, expenditure and income information for the administrative data is registered using the breakdown items.[6] The administrative management system according to [5], wherein the breakdown items are registered one or more times for each administrative data, and include individual expense items to which budget item system items related to the lower-level budget items are associated, and one or more calculation items are registered for each individual expense item and to which budget information is associated, and the expenditure and income information is registered for the individual expense items at the execution stage. [7] The administrative management system according to [6] or [7], wherein the administrative management system tallying one or more of the number of administrative data items, the number of breakdown items, budget information linked to the administrative data, and expenditure and income information linked to the administrative data. [8] An administrative management method for managing administrative data, wherein a computer stores administrative data having a plurality of types of data items, and an attribute-based data item set which is a set of data items set using user attributes and / or a stage-based data item set which is a set of data items set using stages of administrative activities, and receives a display request from a user terminal, and determines the data items to be displayed based on the attribute-based data item set corresponding to the attributes of the user who made the display request and / or the stage-based data item set corresponding to the stage in the administrative activity of the user who made the display request, and performs display processing. [9] A computer program that causes the computer to execute the administrative management method described in [8].

[0008] The invention according to [1] makes it possible to present administrative data according to the attributes of the user, thereby enabling administrative activities to be promoted efficiently.

[0009] The invention of [2] makes it possible to compare data items when newly registering or assessing administrative data, thereby enabling administrative activities to be promoted efficiently.

[0010] The invention related to [3] makes it possible to compile administrative data and grasp the progress of administrative activities based on systematic items, thereby enabling administrative activities to be promoted efficiently.

[0011] The invention according to [4] makes it possible to determine the data items to be output depending on the type of form, thereby efficiently promoting administrative activities.

[0012] According to the invention of [5], it is possible to associate information registered at the budget preparation stage with information registered at the budget execution stage, making it easy to reconcile budgets with expenditures.

[0013] According to the invention of [6], by associating expenditures with individual expense items, it is possible to carry out budget execution efficiently.

[0014] The invention according to [7] makes it possible to efficiently grasp progress, particularly at the execution stage.

[0015] According to the present invention, it is possible to provide a technique for efficiently promoting administrative activities in an administrative organization.

[0016] 1. A system configuration diagram according to the first embodiment. A hardware configuration diagram according to the first embodiment. A conceptual diagram relating to the registration of business information according to the first embodiment. A conceptual diagram relating to the connection of business information according to the first embodiment. A screen display example of a registration screen according to the first embodiment. An example of displayed data items according to the first embodiment. A screen display example of a viewing screen according to the first embodiment. A screen display example of a difference screen according to the first embodiment. A screen display example of a display axis specification screen according to the first embodiment.

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

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

[0019] <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 agencies, ministries, and public organizations, such as those of the national and local governments. In embodiment 1, a local government is used as an example. The administrative management system according to the present invention is used in administrative organizations to operate and manage administrative activities. A policy system is a system of issues divided into three levels: policies, measures, and administrative projects. For example, a division into four or more levels may be used to manage administrative projects, with a level of sub-measures between measures and administrative projects. A policy is a broad group of administrative activities aimed at realizing basic guidelines for addressing specific administrative issues, and indicates the direction and purpose of urban development in an established administrative division (such as a city, ward, town, or village). A policy is a group of administrative activities aimed at realizing specific guidelines based on the basic guidelines of a policy, and indicates the measures and countermeasures for realizing the policy. An administrative project is an administrative project or project that serves as an individual administrative means for realizing the specific policies of a policy. Tasks and projects are implemented by each bureau within an administrative division based on its own budget. In this embodiment, the task system is divided into four levels, with each task and project being further broken down into one or more sub-projects. Sub-projects are specific divisions of tasks and projects as administrative measures related to a task and project.

[0020] An administrative object refers to an object handled in administrative activities. In this embodiment, individual administrative tasks and projects are managed as administrative objects. However, for example, answers to questions from assembly members and committee responses prepared by executive bodies such as administrative agencies, the planning, execution, and evaluation stages of administrative tasks and projects, and issues collected by assemblies, committees, etc. and that serve as the basis for formulating administrative issues for the next term and beyond may also be treated as administrative objects. Furthermore, if the administrative organization is the national government, projects including direct projects and affiliated organization projects, as well as other general administrative activity targets, may be considered administrative objects. Administrative objects are managed as administrative data in a database (DB).

[0021] <1.2. Overview of administrative activities> Here is an example of the flow of administrative activities in a local government. First, in the planning stage, plans for the tasks and projects to be implemented in the next execution year (for example, the following fiscal year) are prepared. Next, in the budget compilation stage, budget requests for the tasks and projects to be implemented in the next execution 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 year, in the execution stage, the budget is executed for the 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.

[0022] 1.3. Definition of Terms, etc. 2. A topic refers to a gradual division of administrative activities carried out with an administrative object as the target. One or more topics may be defined for each type of administrative object. In this embodiment, for example, when an administrative project is the target, multiple chronological divisions such as "Budget Preparation > Request," "Budget Preparation > Assessment," "Budget Preparation > Preliminary Notification," "Budget Preparation > Resolution," "Budget Execution," "Settlement of Accounts," and "Administrative Evaluation" are defined as topics. The above is an example, and different divisions, abstract divisions, and more detailed divisions may be defined. Furthermore, topic divisions may be hierarchically organized into multiple layers. For example, instead of the topic "Budget Preparation > XX," divisions such as "Initial Budget Preparation (hereinafter referred to as "Initial") > XX" and "Supplementary Budget Preparation (hereinafter referred to as "Supplementary") > XX" may be defined. Furthermore, subtopics such as "Initial Budget Preparation (hereinafter referred to as "XX")" and "Supplementary Budget Preparation (hereinafter referred to as "XX")" may be defined in a layer below "Budget Preparation." Furthermore, multiple chronological divisions may also be defined in the lower layers. For example, categories such as "request," "assessment," "unofficial notice," and "resolution" may be defined in the layer below "budget compilation."

[0023] An issue refers to a topic in carrying out administrative activities that occur for 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 for an administrative object of a specific topic or a group of administrative objects that belong to a specific topic.

[0024] A workflow refers to a repeatable, defined flow of administrative activities. In this embodiment, the workflow includes multiple stages WS executed to achieve a certain purpose, and progresses by completing issues assigned to individuals in each stage WSn. The stages of a workflow executed in a certain topic can be understood as smaller stages of administrative activities related to that topic.

[0025] Data items are various data that are registered and managed regarding administrative objects. Mandatory data items are a category of data items that must be registered. Optional data items are a category of data items that have predefined attribute names and allow data values ​​to be entered or the entered data items to be displayed by enabling or disabling them. Additional data items are a category of data items that allow data values ​​to be entered or the entered data items to be displayed by registering unique attribute names.

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

[0027] The administrative management system 1 (administrative management device 2) provides a platform for operating and managing administrative activities related to administrative objects including at least administrative projects. The administrative management device 2 includes, as functional components, an administrative data management unit 21, an issue management unit 23, a tallying processing unit 26, a display processing unit 27, and a setting management unit 28.

[0028] The user terminal 3 is a terminal device used by users belonging to an administrative organization, etc. A plurality of user terminals 3 are installed at least within the administrative organization.

[0029] In this embodiment, users include special officials (such as mayors) within administrative organizations, users of the Finance Division and other secretariat departments, section chiefs, department heads, the Civil Engineering Department (bureau / section) and the Agriculture, Forestry and Fisheries Department (bureau / section), and users and supervisors (section chiefs, department heads, etc.) of original bureaus and original sections. For example, original section users perform tasks such as creating project documents 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, department heads, and special officials perform tasks such as reviewing user deliverables, selecting and prioritizing priority projects based on plans, and assessing budget requests approved by Finance Division users. The administrative management system 1 assigns predetermined operational authority to each user and controls the permission and restriction of predetermined functions according to the operational authority. In particular, users who perform processing at a certain stage of the workflow are referred to as ``persons in charge.''

[0030] 2.2. Hardware Configuration FIG. 2(a) shows a hardware configuration diagram of the administrative management device 2. The administrative management device 2 includes a control unit 201, a storage unit 202, and a communication unit 203 as its hardware configuration. In this embodiment, the administrative management device 2 can be 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-described functional components (21-27) can be realized as a whole.

[0031] The control unit 201 is composed of one or more processors such as a CPU, and controls the overall processing of the administrative management device 2 by executing an administrative management program, an OS (Operating System), and other applications. The storage unit 202 is composed of one or more memories such as an HDD (Hard Disk Drive), SSD (Solid State Drive), flash memory, RAM (Random Access Memory), etc., 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. By executing the administrative management program, the control unit 201 causes the computer to function as the administrative management device 2 and execute the administrative management method.

[0032] In the illustrated example, the database DB is a database server that can be accessed via a communication network NW including an LGWAN, etc., but it may also be realized using, for example, the control unit 201 and 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.

[0033] 2B 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.

[0034] The control unit 901 is composed of one or more processors such as a CPU, and controls the overall processing of 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, mouse, keyboard, etc. The display unit 905 is composed of a display that displays the processing results of the control unit 901, etc.

[0035] 2.3. Display Processing Unit 27 The display processing unit 27 displays the administrative data management platform on the user terminal 3. The administrative data management platform is used for registering, editing, and deleting (hereinafter referred to as "registration") various types of data, as well as for workflow management, data display, data output, and the like, based on requests from the user terminal 3. In this embodiment, the management platform is used in the form of a web browser application. Users use their own accounts to use the management platform, and the information processing described below is executed via the management platform.

[0036] 3.1. Data Structure First, the data structure in the administrative management system according to this embodiment will be described.

[0037] The database DB stores organizational master, user master, policy / measure master, subject master, administrative goal master, and authority master, as well as administrative business information (administrative data) from previous years.

[0038] The organizational master stores organizational structure items that represent a tree-structured organizational structure by linking data items as master data for data items related to organizations within or outside the administrative organization. In this embodiment, the organizational master stores organizational information and department information as organizational structure items. The organizational information stores identification information (organization ID) of the organization and the organization name. The department information stores identification information (department ID) of the department (division, section, office, etc.) within the organization, identification information (organization ID) of the organization to which the department belongs, identification information (department ID) of the higher-level department to which the department belongs, and the department name. The departments to which users belong, as described below, and departments in charge of policies, measures, and administrative projects, etc., are registered in an identifiable manner based on the organizational structure items. The user master stores user information within the organization. The user information includes user identification information (user ID), name, department (organization structure item), etc. Note that user groups, which are a collection of one or more users, may be defined. The user group information may be predefined by, for example, the identification information of the user group (user group ID) and the identification information of the users belonging to the user group, or users having a common attribute such as an organizational structure item may be treated as a user group. The users to be included in the predefined user group may be arbitrarily selectable, or may be selectable from user groups having a common attribute. The user group is specified by an arbitrarily set group name or an attribute name that represents the characteristics of the group.

[0039] The policy / measure master stores policy / measure system items that represent a tree-structured policy / measure system by linking data items as master data for data items related to policies and measures. In this embodiment, the policy / measure master stores policy information and measure information as policy / measure system items. The policy information / measure information includes identification information for the policy / measure (policy ID / measure ID), policy number / measure number, policy name / measure name, responsible department (department, section, etc.), policy purpose / measure purpose, and policy summary / measure summary. Furthermore, the measure information includes identification information for the corresponding main policy (policy ID).

[0040] The item master stores master data for data items representing item system items. In this embodiment, as master data for data items representing the budget item system and the local government financial status survey item system, budget item system items representing the tree-structured budget item system through linkages between data items and local government financial status survey items representing the tree-structured local government financial status survey item system are stored. In this embodiment, the budget item master stores budget item information as budget item system items. The budget item information includes budget item identification information (budget item ID), identification information (budget item ID) of the higher-level budget item to which the budget item belongs, budget item type (in this embodiment, either a subitem, section, or subitem), and budget item name. The budget item type includes subitems (higher-level budget items), which are higher-level items corresponding to the objectives at the time of closing, and subitems (lower-level budget items), which are lower-level items corresponding to the characteristics. When the administrative organization is a national government, items, etc., can be higher-level budget items, and items under the items can be lower-level budget items. The local government financial situation survey item master stores expenditure breakdown purpose information and budget property information as local government financial situation survey items. The expenditure breakdown purpose indicates the purpose of expenditure linked to an administrative project and is used for local government financial situation surveys in the settlement topic. The expenditure breakdown purpose information includes identification information of the expenditure breakdown purpose (expenditure breakdown purpose ID), identification information of the higher-level expenditure breakdown purpose to which the expenditure breakdown purpose belongs (expenditure breakdown purpose ID), identification information of the corresponding budget item (any of the subitems) (budget item ID), type of expenditure breakdown purpose (in this embodiment, there are three types: major classification, medium classification, and minor classification), and expenditure breakdown purpose name. The budget property indicates the property of the budget set under a section or subsection, and the budget property information includes identification information of the budget property (budget property ID), identification information of the higher-level budget property (budget property ID), identification information of the budget item (section or subsection) to which the budget property belongs (corresponds to) (budget item ID), type of budget property (in this embodiment, there are four types: major classification, medium classification, minor classification, and detailed classification), and budget property name.

[0041] The administrative goal master stores administrative goal system items that represent the administrative goal system in a tree structure by linking data items as master data for data items that indicate the administrative goal system. Administrative goals define KPIs for achieving each task or project, i.e., tasks to be achieved during the execution period of the task or project. One or more administrative goals are set for each policy, measure, and task or project, and are structured hierarchically in correspondence with the higher-level policy and measure system. In this embodiment, the administrative goal master stores administrative goal information as administrative goal system items. The administrative goal information includes identification information for the administrative goal (administrative goal ID), identification information for the policy, measure, or task or project to which the administrative goal system item is linked, the content of the administrative goal, and the deadline for achieving the administrative goal.

[0042] 3.2. Master Data Registration The setting management unit 28 accepts input related to organizational information, department information, user information, policy information, measure information, budget item information, expenditure breakdown purpose information, budget nature information, and administrative goal information from the user terminal 3, and registers the information in the database DB.

[0043] <3.3. Registration of business information> Next, the registration of business information in the administrative management system according to this embodiment will be described.

[0044] For each task and project, the budget amount, itemized items (budget item system items) used during execution and associated with expenditure amounts, and the expenditure breakdown purpose and budget nature (local government financial status survey items) used during settlement and used to prepare the local government financial status survey are associated from the budget request stage. In addition, for each task and project, breakdown items are set, which are elements that can be decomposed and are contained within each task and project, such as administrative activities related to the task and project, expenditure items related to the budget's use, and budget funding sources. As breakdown items, one or more subprojects are linked to a task and project to which a subproject (budget item system item) is associated. Individual expenditure items indicating the purpose and destination of the budget expenditure to which the subproject (budget item system item) is associated are linked. Individual expenditure items include estimate items indicating the budget amount, etc., and a funding breakdown indicating the funding source. Furthermore, individual tasks, projects, minor projects, or individual expense items are linked to organizational system items, policy and program system items, item categories, and administrative goal system items. In this embodiment, a data structure is adopted in which tasks, projects, and budget item categories (higher-level budget items) related to sub-items are linked to one or more organizational system items, one or more policy and program system items, one or more administrative goal system items, and individual expense items, which are the breakdown items of the tasks, are linked to budget item categories (lower-level budget items) related to the sub-items. Furthermore, in any topic, labels indicating their contents may be assigned to individual tasks, minor projects, or individual expense items. In this embodiment, a label indicating that a task is a priority project is assigned to a task, and a label indicating that a mandatory expense or a label indicating an increase or decrease in the budget amount for an ongoing project, etc. is assigned to an individual expense item.

[0045] The administrative business information is administrative data related to each administrative business, and is registered for each execution year. In this embodiment, the administrative business information includes basic information related to the administrative business (basic administrative business information), administrative goal information, budget information, financial resource information, and expenditure and income information related to the administrative business. Basic information on administrative projects (basic administrative project information) is information on the content of administrative projects, and includes the basic information's (i.e., administrative project information) identification information (administrative project ID), related administrative data, administrative project name, major policies and measures to which the administrative project belongs (policy and measure system item), project start year, execution (planned) year, budget category (initial budget, supplementary budget number), topic, budget amount for the administrative project, revenue amount for the administrative project, budget name, affiliated bureau / agency (organizational system item), responsible department (organizational system item), accounting category, administrative project status (e.g., "new," "expansion," "reduction," "suspended," "abolished"), section item (higher-level budget item: budget project system item), major classification, medium classification, minor classification of expenditure breakdown purpose (local government financial situation survey item), expense classification, budget amount for the administrative project, etc., as well as optional items such as administrative project purpose, administrative project overview, underlying laws and regulations, related plans and notifications, current situation and issues, project (planned) completion year, remarks, priority issues (administrative goal system item), and zero, one, or multiple additional data items.

[0046] Budget information includes, for example, budget amounts for each topic (e.g., "Budget Preparation > Request," "Budget Preparation > Assessment," "Budget Preparation > Preliminary Notification / Resolution"), individual expense item names, and subdivisions of expense items (budget item system items), as well as major, medium, minor, and detailed budget classifications (local government financial situation survey items). Budget amounts include the requested amount, which is the budget amount estimated at the "request" stage of budget preparation; the assessed amount, which is the budget amount adjusted as necessary from the requested amount at the "assessment" stage; the preliminarily announced budget amount, etc. In this embodiment, each administrative and business information is configured to hold the budget amounts for each stage for each individual expense item it has. Funding information indicates one or more funding sources for each budget amount, and includes, for example, the name of the funding source, the amount of revenue appropriated for the budget information, and subdivisions (budget item system items). For example, revenue amounts are linked to each topic in the same way as budget amounts, and are configured to be able to hold, for example, the revenue request amount, which is the estimated revenue amount at the ``request'' stage of budget preparation, the revenue assessment amount, which is the revenue amount adjusted as necessary from the revenue request amount at the ``assessment'' stage, and the revenue indication amount, which is the ``indicated'' revenue amount.

[0047] In this embodiment, administrative projects are broken down into a four-level tree structure based on the breakdown items (administrative project > minor project > individual expense item > accumulated item). An administrative project has a structure that includes one or more minor projects, and a minor project includes one or more individual expense items. Administrative project information includes administrative project basic information, which is a data item in the administrative project layer that represents the content of the administrative project; minor project information, which is a data item in the minor project layer that represents the content of the minor project; and data items in the individual expense item layer that represent the content of the individual expense item. One or more accumulated items are included in individual expense items, and are registered using accumulated item information that indicates the budget amount for the administrative project or a higher-level breakdown item by being accumulated. Funding breakdowns are included in individual expense items (0 or 1), and are registered using funding breakdown information that indicates the revenue amount for the administrative project or a higher-level breakdown item.

[0048] The minor project information includes various information related to the minor project, such as identification information for the minor project (minor project ID), identification information for related administrative information (administrative project ID), minor project name, minor project overview, minor project status (e.g., "new," "expansion," "reduction," "suspended," "cancelled"), and budget amount for the minor project.

[0049] Individual expense items indicate expense items required for administrative activities related to the corresponding subprojects, and individual expense item information includes identification information for the individual expense item (individual expense item ID), identification information for the related subprojects (subproject ID), individual expense item name, budget amount for the individual expense item, individual expense item group label, individual expense item summary, subsections (sub-budget items: budget item system items), and properties (budget properties: budget item system items). Total items are specific expense items included in individual expense items, and total item information includes identification information for the total item (total item ID), identification information for the related individual expense items (individual expense item ID), total item name, budget amount for each topic, planned execution quarter, total item summary, and total basis (formula, etc.). The funding breakdown indicates the funding source for each individual expenditure item, and funding information includes funding identification information (funding ID), identification information for the related individual expenditure item (individual expenditure item ID), funding name, revenue amount for each topic, funding allocation rate, funding classification, item subsection (budget item: budget item system item), responsible department (organization system item), allocation basis, and allocation reason. In this embodiment, funding information is registered as a funding breakdown for specific funding sources. For one individual expenditure item, if the entire budget amount is covered by general funding sources, no funding information is registered, and if the amount is covered by specific funding sources, or specific funding sources and general funding sources, one piece of funding information is registered. The funding breakdown for general funding sources can be obtained from the difference between the budget amount and the revenue amount, or the budget amount and the funding allocation rate.

[0050] Based on individual expenditure items, or individual expenditure items and estimated items, the details of each task and project can be set from the budget preparation stage. In the execution process described below, the budget item system items and / or local government financial status survey items for this task and project can be specified to execute the budget, eliminating the need to reconcile the budget and expenditures at the settlement stage. The expenditure breakdown purpose and budget nature are items that correspond to higher-level budget items and lower-level budget items, respectively. However, even when the administrative organization is the national government, financial-related items that correspond to higher-level budget items and lower-level budget items can be set as master data and associated with projects and individual expenditure items.

[0051] In this embodiment, the administrative business is subdivided into a four-level tree structure, and the budget amount for an administrative business is determined by the total budget amount of the sub-businesses under the administrative business, the budget amount for a sub-business is determined by the total budget amount of the individual expense items under the sub-business, and the budget amount for an individual expense item is determined by the total budget amount of the accumulated items under the individual expense items. In other words, when registering administrative business information, the administrative data management unit 21 registers the budget amount for the accumulated items, thereby also registering the budget amounts for the individual expense items, sub-businesses, and administrative business. The same applies to revenue amounts.

[0052] 3.4. Administrative Data Management Unit 21 The administrative data management unit 21 accepts input related to various administrative data from the user terminal 3 and registers the administrative data in the database DB. The following describes the registration of administrative business information, which is administrative data related to administrative businesses.

[0053] 3.5. Issue Management Unit 23 The issue management unit 23 registers issues associated with administrative projects or minor projects (administrative objects), responsible parties, and topics. When an issue is registered, the responsible party is notified that the issue has been registered, and the responsible party checks the content of the issue and performs administrative activities such as registering and approving administrative project information. The issue management unit 23 registers issues by storing issue information in a database DB based on a request from a user to create an issue or a request to start a workflow.

[0054] The issue information includes the issue identification information (issue ID), the identification information of the corresponding administrative object (task / project ID), the issue title and content, the person in charge, the issue creator, the issue status, the deadline, attachments, work items, and the issue group identification information (issue group ID). For example, when executing a budget compilation workflow, an issue (issue group) for the topic "Budget compilation > Request" (registering task / project information for initial budget requests) is assigned to users in each original bureau and original division, and issues such as "Budget compilation > Assessment" and "Budget compilation > Preliminary announcement" are assigned to users and heads of the secretariat department. The workflow is completed when a series of issues for each task / project targeted by the issue group are completed.

[0055] The issue management unit 23 sets the issue status. The issue status is, for example, "needs work," "returned," or "completed." For example, the issue management unit 23 changes the issue status in response to a completion operation from the person in charge of the issue. The issue management unit 23 determines the processing status of the workflow based on the processing status of the issue. The processing status of the issue is the issue status of the issue, the person in charge of the issue (stage of the workflow), etc.

[0056] The issue management unit 23 receives a request to register an issue for the "Budget Preparation > Request" topic for the purpose of registering business information, for example, from a user in the secretariat department, with a user in the original bureau or original division as the person in charge, and registers the issue information. This starts the workflow for the "Budget Preparation > Request" topic. The person in charge who receives the issue notification displays the information related to the issue issued to them on their user terminal 3 and registers the business information via the business registration screen. The person in charge enters each data item related to the business information via the business registration screen displayed on the user terminal 3 and sends it to the administrative data management unit 21.

[0057] <3.6. Execution of Workflow> For a specific topic, multiple issues that are executed in stages within the topic are registered, and the workflow is completed when the series of issues is completed. When performing administrative activities for multiple administrative projects or sub-projects (administrative object groups), a set of issues (issue group) is defined for each administrative object belonging to the administrative object group, and the workflow is completed when the series of issues for each administrative object is completed.

[0058] In this embodiment, when a workflow is started, multiple users who will be responsible for each stage of multiple issues that will be executed in stages are designated, and the issues are registered. Issues may be executed in stages by a certain person in charge designating a user who will be responsible for the next stage and registering the issue, or multiple users including at least the first and last people in charge may be designated at the start of the workflow, and issue stages may be inserted during the execution of the workflow. Note that a user may be able to register an issue as the person in charge.

[0059] Note that input of some data items related to administrative and project information is restricted depending on the topic, budget type, and organizational structure item. For example, in the "Budget Preparation > Request" topic, personnel from the original bureau and original division are able to input data items related to project requests (such as the name of the project, the requested amount, and the requested expenditure amount for financial information) from among the administrative and project information, but are unable to input assessment information related to the assessment of the project request (such as the assessed amount and assessed expenditure amount). Personnel from the secretariat department in charge of assessment are able to input assessment information, but are unable to input request information.

[0060] <3.7. Referencing Budgeted Task and Project Information> Task and project information may include the registration of task and project information related to new tasks and projects, and the registration of task and project information related to tasks and projects that have been budgeted or canceled in the past. More specifically, this information includes (1) task and project information for initial budget requests related to new tasks and projects (initial new), (2) task and project information for initial budget requests related to tasks and projects budgeted in the previous year (initial continuing), (3) task and project information for initial budget requests related to tasks and projects implemented every one or more biennial years (initial biennial), and (4) task and project information related to supplementary budgets requested after these have been budgeted (supplementary).

[0061] (1) When registering new business information, the administrative data management unit 21 receives input for data items related to the new business via the business registration screen displayed on the user terminal 3, and registers the new business information. The issue management unit 23 receives a completion operation for the registration of new business information from the person in charge of the issue, and requests the person in charge of the approval stage to implement the issue.

[0062] (2) When registering task and business information (initial continuation), the administrative data management unit 21 copies the data items of task and business information related to each task and business budgeted in the previous year at the start of the workflow or in a topic prior to the "Budget Preparation > Request" topic, and registers the task and business information (initial continuation).The administrative data management unit 21 then accepts input, editing, and deletion of data items related to tasks and businesses budgeted in the previous year, and updates the task and business information (initial continuation).The issue management unit 23 accepts the completion operation of the task and business information (initial continuation) registration from the person in charge of the issue, and requests the person in the approval stage to implement the issue.

[0063] (3) When registering administrative business information (initial biennial), the administrative data management unit 21 accepts the designation of administrative business from the previous year from the person in charge, duplicates the data items of the administrative business information related to the designated administrative business from the previous year, and registers the administrative business information (initial biennial).The administrative data management unit 21 then accepts input, editing, and deletion of the data items related to the designated administrative business from the previous year, and updates the administrative business information (initial biennial).The issue management unit 23 accepts the completion operation for the registration of administrative business information (initial continuation) from the person in charge of the issue, and requests the person in the approval stage to implement the issue.

[0064] (4) When registering administrative business information (corrections), the administrative data management unit 21 accepts the designation of the administrative business for this year from the person in charge, duplicates the data items of the administrative business information related to the designated administrative business for this year, and registers the administrative business information (corrections).The administrative data management unit 21 then accepts input, editing, and deletion of the data items related to the designated administrative business for this year, and updates the administrative business information (corrections).The issue management unit 23 accepts the completion operation of the registration of administrative business information (corrections) from the person in charge of the issue, and requests the person in the approval stage to implement the issue.

[0065] 3 is a conceptual diagram of when new task and business information is registered from task and business information related to tasks and businesses that have been budgeted up to now. The administrative data management unit 21 registers the new task and business information by referring to task and business information related to the initial budget unofficially announced for a certain fiscal year, as well as task and business information related to zero, one, or multiple supplementary budgets unofficially announced for the same task and business in the same fiscal year.

[0066] FIG. 3(a) is a conceptual diagram illustrating the registration of administrative business information (correction) for a supplementary budget request. When newly registering administrative business information (June 2023 correction) for a June supplementary budget request for administrative business 1 for fiscal year 2023, the administrative data management unit 21 references the administrative business information (initial fiscal year 2023) related to the initial budget recorded for administrative business 1 for fiscal year 2023. As shown in the illustrated example, the administrative business information (initial fiscal year 2023) includes various data items in the administrative business layer related to administrative business 1, various data items in the sub-business layers related to sub-businesses A and B, and various data items in the individual expense item layer related to individual expense items A1, A2, and B1, as well as an accumulation item A11 and a funding breakdown A12 included in individual expense item A1, an accumulation item A21 and a funding breakdown A22 included in individual expense item A2, and an accumulation item B11 and a funding breakdown B12 included in individual expense item B1. When newly registering administrative business information related to administrative business 1 (June 2023 amendment), the administrative data management unit 21 duplicates the various data items in the administrative business layer included in the administrative business information related to administrative business 1 (initial fiscal year 2023), the various data items in the sub-business layer related to sub-businesses A and B, and the various data items in the individual expense item layer related to individual expense items A1, A2, and B1, and newly registers administrative business information related to administrative business 1 (June 2023 amendment), and also accepts registrations by users for the administrative business information related to administrative business 1 (June 2023 amendment), and updates the administrative business information related to administrative business 1 (June 2023 amendment). In the illustrated example, the user adds accumulation item A13 and funding breakdown A14 to individual expense item A1, registers new data items for individual expense item A3, adds accumulation item A31 and funding breakdown A32 included in individual expense item A3, deletes various data items in the individual expense item layer related to individual expense items A2 and B1 for which a supplementary budget request is not being made, and updates the administrative business information related to administrative business 1 (June 2023 supplementary budget).

[0067] 3(b) is a conceptual diagram of the case where administrative business information (initial continuation) is registered. When newly registering administrative business information (initial continuation in FY2024) relating to administrative business 1 for the current fiscal year (FY2024), the administrative data management unit 21 references administrative business information (initial FY2023) relating to administrative business 1 for the previous fiscal year (FY2023) as well as administrative business information (June supplementary budget for FY2023) relating to the June supplementary budget allocated for administrative business 1. When newly registering the administrative business information (initial continuation in FY2024) related to the administrative business 1, the administrative data management unit 21 registers the various data items of the administrative business layer included in the administrative business information (June 2023 amendment) related to the administrative business 1, the various data items of the sub-business layer related to the sub-business A, the various data items of the individual expense item layer related to the individual expense items A1 and A3, the accumulation items A13 and A31 included in the individual expense items A1 and A3, the financial resource breakdown A14 and A32, and the sub-business B included in the administrative business information (initial in FY2023). The administrative business information relating to administrative business 1 (initial continuation in fiscal year 2024) is newly registered by duplicating the various data items of the detailed business layer, the various data items of the individual expense item layer relating to individual expense items A2 and B1, the accumulation items A11, A21, B11 included in the individual expense items A1, A2, B1, and the financial resource breakdown A12, A22, B12, and the administrative business information relating to administrative business 1 (initial continuation in fiscal year 2024) is also accepted from users, and the administrative business information relating to administrative business 1 (initial continuation in fiscal year 2024) is updated. When newly registering administrative business information (initial every other year), the administrative data management unit 21 references the administrative business information relating to administrative business 1 for the specified fiscal year as well as the administrative business information relating to the supplementary budget allocated for administrative business 1.

[0068] <3.8. Example of Data Structure Using Related Administrative Data> Figure 4 is a diagram showing an example of the connection between administrative and project information. In this embodiment, administrative and project information for each fiscal year is associated using a reference structure such as that shown in Figure 4. When an administrative and project continues, a common administrative and project ID can be used to group administrative and project information for a group of continuing people. By combining the administrative and project ID with a character string indicating the execution year, administrative and project information for each fiscal year can be uniquely distinguished. When multiple administrative and project information for each initial correction category is registered in the same execution year, as in this embodiment, administrative and project information for each fiscal year can be uniquely distinguished by further combining a character string indicating the initial correction category.

[0069] When a task or project is split or merged, the task and project information is associated with each other using related administrative data. For example, as shown in the figure, if tasks A and B implemented in fiscal year 2022 are merged and a budget request is made for task and project A in fiscal year 2023, in this embodiment, new task and project information (task and project B for fiscal year 2023) is registered, and the task and project ID (02) and execution year (fiscal year 2023) of the task and project information (task and project B for fiscal year 2023) are registered as related administrative data for the task and project information (task and project A for fiscal year 2023). The status of the task and project information (task and project B for fiscal year 2023) is set to "abolished." For example, as shown in the figure, if an administrative project A implemented in fiscal year 2023 is divided and a budget is requested for administrative projects A, C, and D in fiscal year 2024, in this embodiment, administrative project information (administrative projects A, C, and D for fiscal year 2024) is registered, and the administrative project ID (01) and execution year (fiscal year 2024) of the administrative project information (administrative project A for fiscal year 2024) are registered as related administrative data in the administrative project information (administrative projects C and D for fiscal year 2024).

[0070] <3.9. Registration Screen for Administrative Business Information> Next, input of data items related to administrative business information will be described with reference to FIG.

[0071] FIG. 5 shows an example of a registration screen for registering administrative and business information. The display processing unit accepts a request to display the registration screen from the user terminal 3 and displays the registration screen. The registration screen W3 includes input fields for multiple data items related to administrative and business operations, and displays a list of at least some of the data items included in the administrative and business information. The data item input fields include data item input fields for the administrative and business layer, data item input fields for the sub-business layer, and data item input fields for the individual expense item layer. The illustrated example shows an example of a screen display when registering administrative and business information (new). However, when administrative and business information is registered based on administrative and business operations previously budgeted, such as administrative and business information (initial continuation), administrative and business information (initial biennial), or administrative and business information (correction), at least some of the data items for the specified year are duplicated and displayed in a preset state in each input field, ready for editing, deletion, etc. Furthermore, when the item (budget item system item) of an administrative project is entered, some or all of the expenditure breakdown purpose (local government financial situation survey item) is automatically inserted into the input field based on that, or the expenditure breakdown purpose is filtered and displayed in a multiple-choice input field such as a pull-down menu. Furthermore, when the details of an individual expenditure item (budget item system item) are entered, some or all of the nature of the individual expenditure item (budget nature: local government financial situation survey item) is automatically inserted into the input field based on that, or displayed in a multiple-choice input field based on that.

[0072] The data item list may include one or more optional data items in addition to one or more required data items. Furthermore, one or more additional data items may be added in addition to or instead of the optional data items. In this embodiment, when an optional data item or additional data item is added by a user, the data item is added to a data item set (attribute-specific data item set) that can only be viewed by the user group, such as the department to which the user belongs.

[0073] 4.1. Viewing Screen for Administrative Business Information Next, viewing data items related to administrative business information will be described with reference to FIGS.

[0074] The authority master stores viewing authority information indicating viewing authority for administrative data and various data items registered and managed as administrative data. In this embodiment, viewing authority for multiple users and / or user groups is set for each administrative data item and stored as viewing authority information. Furthermore, viewing authority for at least some data items in the administrative data is granted to users who have predetermined attributes among multiple users and / or user groups who are granted viewing authority for the administrative data. Note that viewing authority information may also be set for issues to grant viewing authority. Furthermore, in this embodiment, the viewing authority information is described as being stored in the viewing authority master, but the data structure may also include viewing authority information for each administrative data item or issue.

[0075] A data item set for displaying administrative data defined according to user attributes is called an attribute-specific data item set. In this embodiment, attribute-specific data item sets are defined for optional data items and additional data items in administrative data. Attributes include, for example, the user's department (organizational structure item) and other optional user groups. The display processing unit 27 may perform display processing of administrative data based on a data item set (stage-specific data item set) defined according to the stage of administrative activity, such as a workflow stage, in addition to or instead of the data item set defined according to user attributes.

[0076] 6 is a diagram showing an example of data items displayed according to attribute-specific data item sets. When a user with attribute A requests display processing of administrative business information, all required data items, optional data items 1 and 2, and additional data items A1 and A2 are displayed on the user terminal 3. On the other hand, when a user with attribute B requests display processing of administrative business information, all required data items, optional data items 2 and 3, and additional data items B1 and B2 are displayed on the user terminal 3. Also, when a user with attribute C requests display processing of administrative business information, all required data items and optional data item 1 are displayed on the user terminal 3.

[0077] A data item set for displaying administrative data defined according to the stage of administrative activity is called a stage-specific data item set. Stages of administrative activity are categorized by the topic of an administrative object, the status of an administrative business, the status of an issue, the stage of a workflow, etc. A stage-specific data item set is a collection of data items defined according to one or a combination of multiple administrative activity stages. Stage-specific data item set information that defines the stage-specific data item set is stored in the database (DB). The stage-specific data item set information includes multiple data items included in the data item set and information indicating the stage (topic, workflow stage, etc.).

[0078] The issue management unit 23 registers issue information in which a user requests a person in charge to register data items according to the stage of administrative activity, and the issue management unit 23 associates the issue with the task, project, person in charge, and topic. The designated person in charge checks the registered issue and requests the display of a registration screen for the associated task, project, and topic, and the display processing unit 27 displays the registration screen on the user terminal 3.

[0079] For example, in a budget request (budget preparation > request) workflow, the administrative and business information displayed to a special-class user (such as a chief executive) who is a higher-ranking approver in the workflow can be more macroscopic than the content displayed to users in the original bureau or department or the secretariat. Also, the administrative and business information displayed in the budget request (budget preparation > request) topic can be different from the administrative and business information displayed in the assessment (budget preparation > assessment) topic or the unofficial notice (budget preparation > unofficial notice) topic.

[0080] Figure 7 shows an example of the display of the viewing screen W7 for viewing registered administrative and business information. When a user requests display of administrative and business information, the display processing unit 27 displays the administrative and business information, including zero, one, or more optional data items specified based on the attribute-specific data item set, as well as zero, one, or more additional data items, and the viewing screen W7 is displayed on the user terminal 3. The user can specify the display axis for administrative and business information on the viewing screen W7, which displays information on the administrative and business layer corresponding to the display axis and administrative and business information related to the breakdown items. The display axis is set, for example, by combining the execution year, budget type, and topic (request, assessment, unofficial announcement). Furthermore, by pressing Add Difference on the viewing screen W7, a difference screen W8 is displayed for viewing the registered administrative and business information side by side.

[0081] 4.2. Differential Screen for Task and Business Information Figure 8 shows an example of the differential screen W8. When a user requests the display of the differential screen W8, the display processing unit 27 splits the screen into multiple display frames (two in the illustrated example) for the specific task and business specified by the user on the viewing screen W7, displays the task and business information in each display frame, and the viewing screen W7 is displayed on the user terminal 3. The user can specify the display axis for the task and business information by specifying the display axis for each display frame. Because the task and business information displayed in both display frames includes at least some common data items (e.g., required data items), individual data items can be arranged side by side. For data items (optional data items or additional data items; in the illustrated example, task and business overviews) for which values ​​are registered only on some display axes, the corresponding data item names and margins can be displayed on display axes for which values ​​are not registered, allowing the data items to be aligned between display axes.

[0082] As shown in the illustrated example, for identical differential data items whose values ​​differ for each display axis between the same data items (see the dashed-dotted line in Figure 8), the display processing unit 27 highlights and displays the data items in one or more display frames. Also, for corresponding differential data items whose values ​​differ for each display axis between corresponding data items (see the dashed-dotted line in Figure 8), the display processing unit 27 highlights and displays the data items in one or both display frames. Corresponding differential data items include, for example, requested amount, assessed amount, unofficial amount, revenue requested amount, revenue assessed amount, unofficial revenue amount, etc.

[0083] In the illustrated example, identical difference data items are displayed in chromatic light gray in the display frame of the comparison source, and further, for identical difference data items whose values ​​are numerical (amounts), the text color is changed according to the increase or decrease in the value. Corresponding difference data items are displayed in chromatic light gray in the display frames of the comparison source and comparison destination. It is preferable that corresponding difference data items in the display frames of the comparison source and comparison destination are displayed in a distinguishable highlighted manner, and in the illustrated example, corresponding difference data items of the comparison source are displayed in the same chromatic light gray as identical difference data items, and corresponding difference data items of the comparison destination are displayed in a chromatic light gray different color from the comparison source.

[0084] In FIGS. 7 and 8 , the display axis is changed by manipulating the display axis specification on the viewing screen W7 and the difference screen W8. However, instead of or in addition to the display axis specification, the display axis may be changed using the display axis specification screen W9 shown in FIG. 9 . The display axis specification screen W9 is a screen for specifying a display axis on a timeline. The illustrated example illustrates a case where a display axis is specified for a comparison source and a comparison destination when displaying differences. However, a similar screen display may also be used when specifying an individual display axis. The user scrolls the display axis specification screen W9 and selects a combination of execution year, budget type, and topic arranged on the timeline for the comparison source and one or more comparison destinations to specify the display axis. The display axis specification screen W9 may be arranged, for example, alongside the difference screen W8 (viewing screen W7) or may be transitionable from the difference screen W8 (viewing screen W7).

[0085] 5.1. Execution Processing The administrative data management unit 21 accepts input from the user terminal 3 of the specification of the breakdown items to which sub-items (sub-budget items) are linked, as well as input of expenditure and income information, and registers the breakdown items and expenditure and income information related to the administrative project in association with each other.

[0086] The expenditure and income information is information related to expenditures and / or incomes that is registered at any time during the budget execution stage during the execution period. The expenditure and income information includes identification information for the expenditure or income (expense and income ID), identification numbers for itemized items of the budget to be executed, names of expenditure and income items, expenditure and income amounts, and sub-items (budget subject system items). In this embodiment, individual expenditure items are linked to the expenditure and income information as the budget to be executed, but it is also possible to link estimated items.

[0087] 5.2. Aggregation Processing Unit 26 The aggregation processing unit 26 aggregates the number of administrative projects or subitems, and / or one or more of the budget information, financial resource information, and expenditure / revenue information associated with administrative projects. For example, on a search screen for administrative projects (not shown), the aggregation processing unit 26 aggregates the estimated items and financial resource breakdowns of administrative projects (subitems) searched for using predetermined aggregation axes and conditions, and the display processing unit 27 displays the aggregation results. The aggregation axes include, for example, the execution year, budget type, status, and topic. The conditions may include, for example, one or more of the master data items associated with the budget information (organizational structure items, policy / measure structure items, budget item item, local government financial status survey items, and administrative goal system items), and whether the project is a priority project (priority project label). This allows aggregation processing of the number of administrative projects, budget amounts, revenue amounts, and expenditure amounts across projects. The conditions may also include keywords, amounts, or other numerical values.

[0088] When the tallying unit 26 performs tallying processing on a data item at a higher level in the tree structure, the tallying processing results include the number of tasks, projects, etc. associated with the data items under that data item, as well as budget information and financial resource information. For example, when tallying processing is performed on Policy A (a policy / measure system item), the number of tasks, projects, and revenues under measures A1 to An under Policy A are tallying processing. For example, when tallying processing is performed on Section B (a budget subject system item), the number of individual expense items in Section B, budget amounts, and revenues for the breakdown of financial resources are tallying processing. Furthermore, for example, it is possible to tally the unofficial amounts and expenditure amounts for task / project groups that meet specific conditions, and it is also possible to monitor the status of budget execution at any time during the budget execution stage.

[0089] Second Embodiment Next, a case where various forms relating to administrative objects are generated will be described in a second embodiment. Note that a description of the same configuration as in the first embodiment will be omitted.

[0090] In this embodiment, the administrative data management unit 21 acquires information on the budget compilation and execution of a project at the administrative evaluation stage and generates an administrative evaluation form, which is a form for conducting administrative evaluation. Also, the administrative data management unit 21 acquires information on the budget compilation of a project at the budget compilation stage and generates a budget proposal.

[0091] 6.1. Database DB The database DB according to this embodiment stores organization master, user master, policy / measure master, subject master, authority master, and administrative business information (administrative data), as well as form item master.

[0092] 6.2 Display Screen for Each Form A data item set defined according to the output content of various forms is called a “form-specific data item set.” Forms include, for example, administrative evaluation forms and budget proposals.

[0093] In this embodiment, the form item master stores form-specific data item set information that defines a form-specific data item set. The form-specific data item set information includes the form name and multiple data items included in the data item set.

[0094] When a user specifies a form type and a task or business, or an extraction axis and / or conditions, via the user terminal 3, the display processing unit 27 processes the display of the specified type of form based on the task information stored in the database DB and the form-specific data item set, and displays the form screen on the user terminal 3. If there are data items required to create a form other than the known data items stored in the database, an issue may be registered requesting the person in charge to register the missing data items. The issue may include a link to an input form for the missing data items or the name of the missing data items. The designated person checks the registered issue and requests the display of a registration screen for the associated task, and the display processing unit 27 displays the registration screen on the user terminal 3.

[0095] REFERENCE SIGNS LIST 1 Administrative management system 2 Administrative management device 21 Administrative data management unit 23 Issue management unit 26 Aggregation processing unit 27 Display processing unit 3 User terminal

Claims

1. An administrative management system that manages administrative data, which stores administrative data having multiple types of data items, and attribute-based data item sets which are sets of data items set using user attributes, and / or stage-based data item sets which are sets of data items set using stages of administrative activities, and determines the data items to be displayed based on the attribute-based data item set corresponding to the attributes of the user who made the display request and / or the stage-based data item set corresponding to the stage in the administrative activity of the user who made the display request.

2. The administrative management system of claim 1, which stores the linkage of corresponding administrative data at different points in time, matches the data items of each administrative data, aligns corresponding data items contained in the administrative data, and displays differences in corresponding data items.

3. The administrative management system of claim 1, wherein the administrative data includes data items related to system items defined as master data in a multi-level tree structure, and the system items and aggregation axes including at least the execution year and budget type are used to aggregate the number of administrative data items, the number of detailed items contained in the administrative data, or one or more data items that can be accumulated and are linked to the administrative data.

4. An administrative management system as described in claim 1, which stores a form-specific data item set, which is a collection of the data items required for each form type, and displays and processes a form in which the data items selected based on the form-specific data item set corresponding to a specified form type are laid out.

5. The administrative management system of claim 1, which, for each piece of administrative data, registers budget item system items relating to sub-budget items and detailed items to which budget information is associated at the budget preparation stage, and, at the execution stage, registers expenditure and income information for the administrative data for the detailed items.

6. The administrative management system of claim 5, wherein the detailed items include individual expenditure items, one or more of which are registered for each piece of administrative data and to which budget item system items related to the lower-level budget items are associated, and one or more of which are registered for each individual expenditure item and to which budget information is associated, and wherein the expenditure and income information is registered for the individual expenditure items during the execution stage.

7. An administrative management system as described in claim 5 or 6, which aggregates and processes one or more of the number of administrative data items, the number of detailed items, budget information linked to the administrative data, and expenditure and income information linked to the administrative data.

8. An administrative management method for managing administrative data, comprising: a computer that stores administrative data having a plurality of types of data items, and an attribute-based data item set which is a set of data items set using the attributes of a user, and / or a stage-based data item set which is a set of data items set using the stage of administrative activity; receives a display request from a user terminal; and determines the data items to be displayed based on the attribute-based data item set corresponding to the attributes of the user who made the display request and / or the stage-based data item set corresponding to the stage in the administrative activity of the user who made the display request, and performs display processing.

9. A computer program that causes a computer to execute the administrative management method according to claim 8.

Images