Administrative management system, administrative management method, and computer program

Abstract

To provide a technique for efficiently advancing administrative activities in an administrative organization.SOLUTION: An administrative management system for managing administrative data: stores administrative data including a plurality of types of data items, an attribute-specific data item set, which is a set of data items set using attributes of users, and / or a step-specific data item set, which is a set of data items set using steps of administrative activities; and determines the 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 who has made a display request and / or the step-specific data item set corresponding to a step in the administrative activities of the user who has made the display request.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 manages administrative data, storing administrative data having a plurality of types of data items, 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; An administrative management system that determines the data items to be displayed based on the attribute-specific data item set corresponding to the attributes of the user who made the display request, and / or the stage-specific data item set corresponding to the stage in the administrative activity of the user who made the display request. [2] storing the linkages between corresponding administrative data at different points in time; The administrative management system described in [1] compares 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 data includes data items related to system items defined as master data in a multi-level tree structure, The administrative management system described in [1] or [2] compiles and processes 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, based on the system items and aggregation axes that include at least the execution year and budget type. [4] storing a set of data items for each document type, which is a set of the data items required for each document type; An administrative management system described in any of [1] to [3], which 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] For each administrative data, at the budget preparation stage, register the budget item system items related to the sub-budget items and the breakdown items to which the budget information is associated; An administrative management system according to any one of [1] to [4], which, in the execution stage, registers expenditure and income information for administrative data for the aforementioned detailed items. [6] The detailed items include individual expenditure items, one or more of which are registered for each 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, The administrative management system according to [5], wherein, in the execution stage, the expenditure and income information is registered for the individual expenditure items. [7] An administrative management system according to [6] or [7], 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 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; An administrative management method which accepts a display request from a user terminal, determines the data items to be displayed based on the attribute-specific data item set corresponding to the attributes of the user who made the display request and / or the stage-specific data item set corresponding to the stage in the administrative activity of the user who made the display request, and processes the display. [9] A computer program that causes the computer to execute the administrative management method described in [8].

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

[0009] [2] The invention relates to a system that enables comparison of data items when newly registering or assessing administrative data, thereby enabling efficient promotion of administrative activities.

[0010] [3] The invention of the present invention 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] [4] The invention relates to determining the data items to be output according to the type of document, thereby enabling administrative activities to be promoted efficiently.

[0012] [5] The invention relates to a method for matching information registered at the budget preparation stage with information registered at the budget execution stage, making it easier to reconcile budgets with expenditures.

[0013] [6] The invention relates to efficient budget execution by matching expenditures to individual expense items.

[0014] The invention related to [7] makes it possible to more efficiently monitor progress, particularly during the execution stage. Effect of the Invention

[0015] 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]

[0016] [Figure 1] FIG. 1 is a system configuration diagram according to a first embodiment. [Diagram 2] FIG. 1 is a hardware configuration diagram according to the first embodiment. [Diagram 3] FIG. 2 is a conceptual diagram regarding registration of business and project information according to the first embodiment. [Figure 4] FIG. 2 is a conceptual diagram showing connections between pieces of business and project information according to the first embodiment. [Diagram 5] 6 shows an example of a registration screen display according to the first embodiment. [Figure 6] 6 shows an example of displayed data items according to the first embodiment. [Figure 7] 4 is a screen display example of a viewing screen according to the first embodiment. [Figure 8] 6 is a screen display example of a difference screen according to the first embodiment. [Figure 9] 6 is a screen display example of a display axis designation screen according to the first embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0017] <Embodiment 1> 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.

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

[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 offices, ministries, and public organizations of the country and local governments, and a local government is taken as an example in embodiment 1. 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 layers: policy, policy measures, and business operations. For example, a layer of sub-policies may be set between policies and business operations, and four or more layers may be set up to manage business operations. 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 individual administrative procedures and projects for realizing specific policies in policies. Tasks and projects are implemented by each bureau in an administrative division based on the budget of each bureau. In this embodiment, the task system is divided into four hierarchical levels, with each task and project being further broken down into one or more sub-projects. Sub-projects are specific categories that break down tasks and projects as administrative procedures related to tasks and projects.

[0020] An administrative object refers to an object handled in administrative activities. In this embodiment, individual business operations are managed as administrative objects, but for example, plenary session responses and committee responses prepared by executive agencies such as administrative agencies in response to questions from legislators, planning, execution, and evaluation stages of business operations, and issues collected in assemblies and committees and serving as the basis for planning administrative issues for the next and subsequent periods may also be treated as administrative objects. In addition, when the administrative organization is the nation, projects including direct projects and affiliated organization projects, and other general objects of administrative activities can be administrative objects. Administrative objects are managed as administrative data in a database DB.

[0021] <1.2. Overview of administrative activities> An example of the flow of administrative activities in a local government will be explained. First, in the planning stage, plans for tasks and projects to be implemented in the next 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 execution fiscal year are prepared, the budget requests are assessed, a budget proposal is prepared, and the proposal is submitted to the assembly. Then, when the execution fiscal year arrives, in the execution stage, the budget is executed for tasks and projects approved by the assembly. In the evaluation stage, administrative evaluation reports are prepared for tasks and projects that have been executed.

[0022] <1.3. Definitions of terms etc.2> A topic refers to a gradual 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 project is the object, multiple divisions arranged chronologically, such as "budget preparation > request," "budget preparation > assessment," "budget preparation > preliminary announcement," "budget preparation > resolution," "budget execution," "settlement of accounts," and "administrative evaluation," are defined as topics. The above is one example, and divisions different from these, abstract divisions, detailed divisions, etc. may be defined. Topics may be subdivided by hierarchizing the topics into multiple layers. For example, instead of the topic "budget compilation > ____", categories such as "initial budget compilation (hereinafter referred to as "initial") > ____" and "supplementary budget compilation (hereinafter referred to as "supplementary") > ____" may be defined, or subtopics of "initial > ____" and "supplementary > ____" may be defined in a layer under "budget compilation". In addition, 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 compilation".

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

[0024] A workflow means a repeatable 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 the person in charge at each stage WSn. The stages of the workflow executed in a certain topic are understood to be finer stages of administrative activities related to the topic.

[0025] Data items are various pieces of data that are registered and managed regarding administrative objects. The required data items are classified into data items that must be registered. An optional data item is a category of data item for which the attribute name is defined in advance and which allows the input of a data value or the display of the input data item by enabling or disabling the attribute name. The additional data item is a category of data item for which a unique attribute name can be registered and data values ​​can be input and the input data items can be displayed.

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

[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 a user who belongs to an administrative organization. A plurality of user terminals 3 are installed at least within the administrative organization.

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

[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, 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-27) can be realized as a whole.

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

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

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

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

[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, etc.") 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. A user uses the management platform by using his or her own account, and information processing, which will be described later, 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 data, user master data, policy and measure master data, subject master data, administrative goal master data, and authority master data, as well as administrative business information (administrative data) from previous years.

[0038] The organizational master stores organizational structure items that represent an organizational structure in a tree structure by linking data items as master data of data items related to organizations within or outside an administrative organization. In this embodiment, the organizational master stores organization 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 a department (division, section, etc.) in 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 department to which the user belongs, which will be described later, and the department in charge of policies, measures, and business operations, etc. are registered in an identifiable manner in various information based on the organizational structure items. The user master stores user information within an organization. The user information includes the user's identification information (user ID), name, department (organizational structure item), 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 such as an organizational structure item may be treated as a user group. Users to be included in a predefined user group may be arbitrarily selectable, 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.

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

[0040] The subject master stores master data of data items that indicate subject system items. In this embodiment, as master data of data items that indicate the budget subject system and the local financial situation survey item system, budget subject system items that represent the budget subject system in a tree structure by linking data items, and local financial situation survey items that represent the local financial situation survey item system in a tree structure are stored. In this embodiment, the budget item master stores budget item information as a budget item system item. The budget item information includes identification information of the budget item (budget item ID), identification information of the higher-level budget item to which the budget item belongs (budget item ID), budget item type (in this embodiment, either sub-item or section), and budget item name. The budget item type includes sub-item items (higher-level budget items), which are higher-level items corresponding to the purpose at the time of settlement, and sections (lower-level budget items), which are lower-level items corresponding to the nature. When the administrative organization is a nation, 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. 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. 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 item items) (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), the type of budget property (in this embodiment, there are four types: major classification, medium classification, minor classification, and detailed classification), and the budget property name.

[0041] In the administrative objective master, administrative objective system items that represent the administrative objective system in a tree structure by linking data items are stored as master data of data items that indicate the administrative objective system. Administrative objectives define KPIs for the achievement of each task or project, that is, tasks to be achieved during the execution period of the task or project, and one or more administrative objectives are set for each policy, measure, and task or project, and adopt a hierarchical structure corresponding to the higher-level policy and measure system. In this embodiment, administrative objective information is stored in the administrative objective master as an administrative objective system item. The administrative objective information has identification information of the administrative objective (administrative objective ID), identification information of the policy, measure, or task or project to which the administrative objective system item is linked, the content of the administrative objective, and the deadline for achieving the administrative objective, etc.

[0042] <3.2. Registering master data> 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, etc.

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

[0044] For administrative projects, the budget amount, item / subdivision details (budget subject system items) that are used at the time of execution and correspond to the expenditure amount, and the expenditure breakdown purpose and budget nature (local government financial situation survey items) that are used at the time of closing the accounts are associated with the local government financial situation survey from the budget request stage. In addition, for each task or project, breakdown items are set, which are elements that can be decomposed and are contained within each task or project, such as administrative activities related to the task or project, expenditure items related to the budget use, and budget financial sources. As detailed items, one or more sub-projects are linked to an administrative project that is associated with a section item (budget item system item). A sub-project is linked to an individual expenditure item that indicates the purpose and destination of the budget expenditure that is associated with a sub-section (budget item system item). An individual expenditure item includes an accumulation item that indicates the budget amount, etc., and a financial source breakdown that indicates the source of the funds. In addition, organizational system items, policy and program system items, item categories, and administrative goal system items are linked to individual task projects, subprojects, or individual expenditure items. In this embodiment, one or more organizational system items, one or more policy and program system items, one or more administrative goal system items, and budget item categories (higher-level budget items) related to sub-items are linked to task projects, and budget item categories (lower-level budget items) related to sub-items are linked to individual expenditure items, which are the sub-items. In addition, in any topic, a label indicating its content may be set to individual task projects, subprojects, or individual expenditure items. In this embodiment, a label indicating that the task project is a priority project is set to the task project, and a label indicating that the expenditure item is a mandatory expense or a label indicating an increase or decrease in the budget amount of a continuing project, etc. is set to the individual expenditure items.

[0045] The business information is administrative data related to each business and is registered for each execution year. In this embodiment, the business information includes basic information related to the business (basic business information), administrative goal information, budget information, financial resource information, and expenditure and income information related to the business. Basic information on business operations (basic information on business operations) is information on the contents of business operations, and includes basic information (i.e., business operation information) identification information (business operation ID), related administrative data, business operation name, major policy / measure to which the business operation belongs (policy / measure system item), project start year, execution (planned) year, budget category (initial budget, supplementary budget number), topic, budget amount of business operation, revenue amount of business operation, budget name, affiliated department / agency (organization system item), responsible department (organization system item), accounting category, business operation status, etc. The budget for each project includes the status of each project (for example, "new", "expansion", "reduction", "suspended", "abolished"), item (higher-level budget item: budget item system item), major / medium / minor classifications for expenditure breakdown purposes (local government financial situation survey items), expense classification, budget amount for each project, etc., as well as optional items such as the purpose of the project, overview of the project, legal basis, related plans / notices, current situation / issues, project completion (planned) fiscal year, remarks, priority issues (administrative goal system item), and 0, 1 or multiple additional data items, etc.

[0046] The budget information includes, for example, budget amounts for each topic (e.g., "budget preparation > request", "budget preparation > assessment", "budget preparation > preliminary announcement and resolution"), individual expenditure item names, and subdivisions of expenditure items (budget subject matter system items), as well as major, medium, minor and detailed classifications of budget characteristics (local government financial situation survey items). The budget amounts are 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 preliminary announcement amount, which is the budget amount "preliminarily announced", etc., and in this embodiment, each business information is configured to be able to hold the budget amounts for each stage for each individual expenditure item it has. The financial resource information indicates one or more financial resources for each budget amount, and includes, for example, the name of the financial resource, the amount of revenue appropriated to the budget information, and sub-items (budget item system items). For example, the amount of revenue is also linked to each topic in the same way as the budget amount, and is configured to be able to hold, for example, the revenue request amount, which is the amount of revenue estimated at the "request" stage of budget preparation, the revenue assessment amount, which is the amount of revenue adjusted as necessary from the revenue request amount at the "assessment" stage, the revenue forecast amount, which is the amount of revenue "tentatively forecasted", respectively.

[0047] In this embodiment, the administrative business is divided into a four-level tree structure by the breakdown items (administrative business > minor business > individual expense item > accumulated item). The administrative business adopts a structure including one or more minor businesses, and the minor business includes one or more individual expense items, and the administrative business information includes administrative business basic information, which is a data item of the administrative business layer that represents the contents of the administrative business, minor business information, which is a data item of the minor business layer that represents the contents of the minor business, and data items of the individual expense item layer that represents the contents of the individual expense item. One or more accumulated items are included in the individual expense items, and are registered by the accumulated item information that indicates the budget amount of the administrative business or the higher-level breakdown item by being accumulated. The financial resource breakdown is included 0 or 1 in the individual expense items, and is registered by the financial resource breakdown information that indicates the revenue amount of the administrative business or the higher-level breakdown item.

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

[0049] An individual expenditure item indicates an expenditure item required for administrative activities related to the corresponding sub-project, and individual expenditure item information includes identification information of the individual expenditure item (individual expenditure item ID), identification information of the related sub-project (sub-project ID), individual expenditure item name, budget amount of the individual expenditure item, individual expenditure item group label, individual expenditure item summary, sub-sections (sub-budget items: budget item system items), and properties (budget properties: budget item system items). An accumulation item is a specific expenditure item included in an individual expenditure item, and accumulation item information includes identification information of the accumulation item (accumulation item ID), identification information of the related individual expenditure item (individual expenditure item ID), accumulation item name, budget amount for each topic, planned execution quarter, accumulation item overview, and accumulation basis (formula, etc.). The financial resource breakdown indicates the financial resources of individual expenditure items, and financial resource information includes identification information of the financial resource (financial resource ID), identification information of the related individual expenditure item (individual expenditure item ID), financial resource name, revenue amount for each topic, financial resource allocation rate, financial resource classification, item item subsection (budget subject: budget subject system item), responsible department (organizational system item), allocation basis, and allocation reason. In this embodiment, the financial resource information is registered as a financial resource breakdown related to specific financial resources, and when all the budget amount for one individual expenditure item information is covered by general financial resources, no financial resource information is registered, and when it is covered by specific financial resources, or specific financial resources and general financial resources, one piece of financial resource information is registered. The financial resource breakdown related to general financial resources is obtained from the difference between the budget amount and the revenue amount, or the budget amount and the financial resource allocation rate.

[0050] Based on individual expenditure items, or individual expenditure items and estimated items, the details for a task or 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 or project can be specified to execute the budget, eliminating the need to reconcile budgets 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, but 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 tasks and projects are subdivided into a four-level tree structure, and the budget amount for a task and project is given by the total of the budget amounts for the minor projects under the task and project, the budget amount for a minor project is given by the total of the budget amounts for the individual expense items under the minor project, and the budget amount for an individual expense item is given by the total of the budget amounts for the accumulated items under the individual expense items. In other words, when registering task and project information, the administrative data management unit 21 registers the budget amounts for the accumulated items, thereby also registering the budget amounts for the individual expense items, minor projects, and task and project information. The same applies to the amount of revenue.

[0052] <3.4. Administrative Data Management Division 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, etc. The following describes the registration of business / project information, which is administrative data related to business / projects.

[0053] <3.5. Issue Management Department 23> The issue management unit 23 registers issues associated with business operations or minor operations (administrative objects), persons in charge, and topics. 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 such as registering business operation information and approving it. 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] Issue information includes issue identification information (issue ID), corresponding administrative object identification information (task ID), issue title and content, person in charge, issue creator, issue status, deadline, attachments, work items, and issue group identification information (issue group ID). For example, when executing a budget compilation workflow, an issue (issue group) with the topic "Budget compilation > Request" (registration of task information for initial budget request) is assigned to users of each original bureau and original division, issues such as "Budget compilation > Assessment" and "Budget compilation > Preliminary Notice" are assigned to users and heads of the secretariat department, and the workflow is completed when a series of issues for each task 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", "completed", etc. 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 accepts a registration request for an issue for the topic "Budget preparation > Request" for the purpose of registering business information from, for example, 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 topic "Budget preparation > Request". The person in charge who has received a notification related to the issue displays the information related to the issue issued to him / her on the 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 transmits it to the administrative data management unit 21.

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

[0058] In this embodiment, when starting a workflow, multiple users who will be in charge of each stage of multiple issues that will be executed in stages are designated, and the issues are registered. An issue may be executed in stages by a certain person in charge designating a user who will be in charge of the next stage and registering the issue, or multiple users including at least the first and last person in charge may be designated at the start of the workflow, and an issue stage 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 task and project information is restricted depending on the topic, budget type, and organizational structure item. For example, in the "Budget Preparation > Request" topic, a person in charge of the original bureau and original division is able to input data items related to project requests (task and project name, requested amount, requested expenditure amount of financial resources information, etc.) from among task and project information, but cannot input assessment information related to the assessment of the project request (assessed amount, assessed expenditure amount, etc.). A person in the secretariat department in charge of assessment is able to input assessment information, but cannot input request information.

[0060] <3.7. Reference to budgeted business information> There are cases where task and project information is registered for new tasks and projects, and cases where task and project information is registered for tasks and projects that have been budgeted or canceled in the past. More specifically, this includes (1) task and project information for initial budget requests for new tasks and projects (initial new), (2) task and project information for initial budget requests for tasks and projects budgeted for the previous year (initial continuing), (3) task and project information for initial budget requests for tasks and projects implemented every one or several years (initial biennial), and (4) task and project information for supplementary budgets requested after the above have been budgeted (supplementary).

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

[0062] (2) When registering task / business information (initial continuation), the administrative data management unit 21 copies the data items of task / business information related to each task / 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 / business information (initial continuation). Then, it accepts input, editing, and deletion of data items related to tasks / business budgeted in the previous year, and updates the task / business information (initial continuation). The issue management unit 23 accepts the completion operation of the task / business information (initial continuation) registration from the person in charge of the issue, and makes a request to 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 person in charge, copies the data items of the administrative business information related to the designated administrative business of the past 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 of the past year, and updates the administrative business information (initial biennial).The issue management unit 23 accepts the completion operation of the registration of administrative business information (initial continuation) from the person in charge of the issue, and makes a request to 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 the current year from the person in charge, copies the data items of the administrative business information related to the designated administrative business for the current 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 the current 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 makes a request to the person in the approval stage to implement the issue. Includes:

[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 new task and business information by referring to task and business information related to the initial budget preliminarily announced for a certain fiscal year, as well as task and business information related to zero, one or multiple supplementary budgets preliminarily announced for the same task and business in the same fiscal year.

[0066] FIG. 3(a) is a conceptual diagram of the case where business information (correction) for a supplementary budget request is registered. When newly registering business information (June 2023 correction) for a June supplementary budget request for business 1 in fiscal year 2023, the administrative data management unit 21 refers to business information (initial fiscal year 2023) related to the initial budget recorded for business 1 in fiscal year 2023. As shown in the illustrated example, the business information (initial fiscal year 2023) includes various data items of the business layer related to business 1, various data items of the sub-business layers related to sub-businesses A and B, and various data items of the individual expenditure item layers related to individual expenditure items A1, A2, and B1, as well as the accumulation item A11 and financial resource breakdown A12 included in the individual expenditure item A1, the accumulation item A21 and financial resource breakdown A22 included in the individual expenditure item A2, and the accumulation item B11 and financial resource breakdown B12 included in the individual expenditure item B1. When newly registering administrative and business information related to administrative and business project 1 (June amendment for fiscal year 2023), the administrative data management unit 21 duplicates the various data items of the administrative and business layer included in the administrative and business information related to administrative and business project 1 (initial fiscal year 2023), the various data items of the sub-business layer related to sub-projects A and B, and the various data items of the individual expense item layer related to individual expense items A1, A2, and B1, to newly register the administrative and business information related to administrative and business project 1 (June amendment for fiscal year 2023), and accepts registrations, etc. by users for the administrative and business information related to administrative and business project 1 (June amendment for fiscal year 2023), and updates the administrative and business information related to administrative and business project 1 (June amendment for fiscal year 2023). 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] Fig. 3(b) is a conceptual diagram when registering business and project information (initial continuation). When newly registering business and project information (initial continuation in FY2024) related to business and project 1 of the current fiscal year (FY2024), the administrative data management unit 21 refers to business and project information (initial FY2023) related to business and project 1 of the previous fiscal year (FY2023), as well as business and project information related to the June supplementary budget recorded for business and project 1 (June supplementary budget in FY2023). When newly registering the administrative business information related to the administrative business 1 (initial continuation in FY2024), the administrative data management unit 21 registers various data items of the administrative business layer included in the administrative business information related to the administrative business 1 (June 2023 amendment), various data items of the sub-business layer related to the sub-business A, various data items of the individual expense item layer related to the individual expense items A1 and A3, the accumulated items A13 and A31, the financial resource breakdown A14 and A32 included in the individual expense items A1 and A3, and the sub-business B included in the administrative business information (initial FY2023). Various data items in the detailed project layer, various data items in the individual expense item layer related to individual expense items A2 and B1, and accumulation items A11, A21, B11 included in individual expense items A1, A2, B1, and financial resource breakdown A12, A22, B12 are duplicated to newly register administrative and business information related to administrative and business 1 (initial continuation in FY2024), and the administrative and business information related to administrative and business 1 (initial continuation in FY2024) is accepted from users for registration, etc., and the administrative and business information related to administrative and business 1 (initial continuation in FY2024) is updated. In addition, when newly registering administrative and business information (initially every other year), the administrative data management unit 21 refers to the administrative and business information related to administrative and business 1 for the specified fiscal year, as well as the administrative and business information related to the supplementary budget recorded for administrative and business 1.

[0068] <3.8. Example of data structure based on related administrative data> FIG. 4 is a diagram showing an example of the connection of task and business information. In this embodiment, task and business information for each year is associated by a reference structure as shown in FIG. 4. When a task and business continues, a common task and business ID can be used to group the task and business of the continuing group of people. By combining the task and business ID with a character string indicating the execution year, task and business for each year can be uniquely distinguished. When multiple task and business information are registered for each initial correction category in the same execution year as in this embodiment, task and business for each year can be uniquely distinguished by further combining a character string indicating the initial correction category.

[0069] When a task or project is divided or merged, task and project information is associated with each other by related administrative data. For example, as shown in the figure, when task and project A and B implemented in fiscal year 2022 are merged and a budget is requested 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 in 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. Administrative business information registration screen> Next, the input of data items relating to business / project information will be described with reference to FIG.

[0071] FIG. 5 is a screen display example of a registration screen for registering business information. The display processing unit accepts a screen display request for the registration screen from the user terminal 3 and displays the registration screen. The registration screen W3 has input fields for a plurality of data items related to business, and displays a list of at least some of the data items included in the business information. The data item input fields include data item input fields for the 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 is a screen display example when registering business information (new). However, when business information is registered based on business information budgeted in the past, such as business information (initial continuation), business information (initial biennial), and business information (correction), at least some of the data items for the specified same year are duplicated and displayed in a preset state in each input field so that they can be edited, deleted, etc. In addition, when the item (budget item system item) of the business operation is input, part 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 presented in a multiple-choice input field such as a pull-down menu. Furthermore, when the details (budget item system item) of an individual expenditure item are input, part 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 presented in a multiple-choice input field after filtering.

[0072] The data item list may include one or more optional data items in addition to one or more required data items. Also, 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 be viewed only by a user group such as a department to which the user belongs.

[0073] <4.1. Business information viewing screen> Next, the browsing of data items related to the business / project 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, and stored as viewing authority information. In addition, viewing authority is granted to users who have a specified attribute among multiple users and / or user groups who are granted viewing authority for the administrative data, for at least some data items in the administrative data. In addition, viewing authority information may be set for an issue to grant viewing authority. In the present embodiment, the viewing authority information is stored in the viewing authority master, but each administrative data or issue may have a data structure including viewing authority information.

[0075] A data item set for displaying administrative data defined according to the attributes of a user 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. An attribute is, for example, the department to which the user belongs (organizational system item) or any other user group. Note that 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 the attributes of the user.

[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 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 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 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 and processing administrative data defined according to the stage of administrative activity is called a stage-specific data item set. The stages of administrative activity are categorized by the topic of administrative objects, business status, issue status, workflow stage, etc. A stage-specific data item set is a collection of data items defined according to any one of these, 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. 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 activities, and which corresponds to the business, person in charge, and topic. The designated person in charge checks the registered issue and requests to display a registration screen for the corresponding business, and the display processing unit 27 causes the user terminal 3 to display the registration screen.

[0079] For example, in a budget request (budget preparation > request) workflow, task and business information can be displayed to special-class users (such as the head of the local government) who are higher-ranking approvers in the workflow, at a more macro level than the content displayed to users in the original bureau or department or the secretariat. Also, the task and business information displayed in the budget request (budget preparation > request) topic can be different from the task and business information displayed in the assessment (budget preparation > assessment) topic or the unofficial notice (budget preparation > unofficial notice) topic.

[0080] FIG. 7 is a screen display example of a viewing screen W7 for viewing registered business information. When a user requests display processing of business information, the display processing unit 27 displays business information including 0, 1, or more arbitrary data items specified based on the attribute-specific data item set, and 0, 1, or more additional data items, and the viewing screen W7 is displayed on the user terminal 3. The user specifies the display axis of the business on the viewing screen W7, and the information of the business layer corresponding to the display axis and the business information related to the detailed items are displayed. The display axis is set by a combination of, for example, execution year, budget type, and topic (request, assessment, unofficial announcement). In addition, by pressing Add difference on the viewing screen W7, a difference screen W8 for viewing the registered business information side by side is displayed.

[0081] <4.2. Difference screen for business information> FIG. 8 is a screen display example of the difference screen W8. When a user requests display processing of the difference screen W8, the display processing unit 27 divides the screen into multiple (two in the illustrated example) display frames for a specific task or business designated by the user on the viewing screen W7, processes the task or 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 of the task or business information by specifying the display axis of the task or business for each display frame. The task or business information displayed on both display frames has at least some common data items (mandatory data items, etc.), so that the individual data items can be arranged side by side. For data items (optional data items or additional data items; in the illustrated example, task or business overview) 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, so that the data items can be aligned between the 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 dashed line in FIG. 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 dashed line in FIG. 8), the display processing unit 27 highlights and displays the data items in one or both display frames. Corresponding differential data items are, for example, requested amount, assessed amount, forecast amount, revenue requested amount, revenue assessed amount, revenue forecast amount, etc.

[0083] In the illustrated example, identical difference data items are displayed in chromatic light ink 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 ink 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 with highlighting so that they can be distinguished, and in the illustrated example, corresponding difference data items of the comparison source are displayed in the same chromatic light ink as identical difference data items, and corresponding difference data items of the comparison destination are displayed in a chromatic light ink different from that of the comparison source.

[0084] In Figs. 7 and 8, the display axis is changed by operating the display axis specification on the viewing screen W7 and the difference screen W8, but instead of or in addition to the display axis specification, the display axis may be changed by 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, but a similar screen display may be performed 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 is arranged, for example, alongside the difference screen W8 (viewing screen W7) or is configured to be transitionable from the difference screen W8 (viewing screen W7).

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

[0086] The expenditure and income information is information related to expenditures and / or income 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, expenditure and income item names, expenditure and income amounts, and sub-items (budget subject system items), etc. 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. Counting Processing Unit 26> The tallying processing unit 26 tallying the number of business projects or itemized items, and / or one or more of budget information, financial resource information, and expenditure and income information linked to the business projects. For example, on a search screen for business projects (not shown), the calculation items and financial resource details of business projects (subprojects) searched for using a predetermined tallying axis and conditions are tallying processing, and the display processing unit 27 displays the tallying processing results. The tallying axis is, for example, the execution year, budget type, status, and topic. The conditions can include, for example, one or more of master data items (organizational system items, policy and measure system items, budget item system items, local government financial status survey items, and administrative goal system items) associated with the budget information, and whether or not it is a priority project (priority project label). This allows the number of business projects, budget amounts, revenue amounts, and expenditure amounts to be tallying processing across projects. The conditions may also be keywords, amounts, other numerical values, and the like.

[0088] When the tallying unit 26 performs tallying for a data item at a higher level in the tree structure, the tallying results include the number of tasks and projects, etc., to which the data items under the data items correspond, as well as budget information and financial resource information. For example, when tallying for policy A (policy / measure system item), the number of tasks and projects under measures A1 to An under policy A, budget amounts, and revenue amounts are tallying. For example, when tallying for section B (budget subject system item), the number of individual expenditure items in section B, budget amounts, and revenue amounts of the financial resource breakdown are tallying. In addition, for example, it is possible to tally up the provisionally indicated amounts and expenditure amounts for task and project groups that meet certain conditions, and it is also possible to monitor the status of budget execution at any time during the budget execution stage.

[0089] <Embodiment 2> Next, a case where various forms related to administrative objects are generated will be described in embodiment 2. Note that a description of the same configuration as embodiment 1 will be omitted.

[0090] In this embodiment, the administrative data management unit 21 acquires information on the budget compilation and execution of projects 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 projects at the budget compilation stage, and generates a budget proposal document.

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

[0092] <6.2. Display screen for each report> A data item set defined according to the output contents of various forms is called a “form-specific data item set.” Forms are, 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 a form name and a plurality of data items included in the data item set.

[0094] When a user specifies a form type and a task or an extraction axis and / or a condition via the user terminal 3, the display processing unit 27 processes and displays the form of the specified type based on the task information stored in the database DB and the data item set for each form, 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 to request 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 and the name of the missing data items. The specified person in charge checks the registered issue and requests the display of a registration screen related to the associated task, and the display processing unit 27 displays the registration screen on the user terminal 3. [Explanation of symbols]

[0095] 1. Administrative Management System 2 Administrative management device 21 Administrative Data Management Department 23 Issue Management Department 26 Counting Processing Unit 27 Display processing section 3. User terminal

Claims

1. An administrative management system for managing administrative data, storing administrative data having a plurality of types of data items, 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; An administrative management system that determines the data items to be displayed based on the attribute-specific data item set corresponding to the attributes of the user who made the display request, and / or the stage-specific data item set corresponding to the stage in the administrative activity of the user who made the display request.

2. storing the linkages of corresponding administrative data at different points in time; 2. The administrative management system according to claim 1, further comprising: matching the data items of each administrative data, arranging corresponding data items contained in the administrative data, and displaying differences in corresponding data items.

3. The administrative data includes data items related to system items defined as master data in a multi-level tree structure, The administrative management system of claim 1, which aggregates 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, based on the system items and an aggregation axis that includes at least the execution year and budget type.

4. storing a data item set for each form, which is a set of the data items required for each form type; 2. The administrative management system according to claim 1, further comprising: a display process for 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. For each administrative data, at the budget preparation stage, the budget item system items related to the sub-budget items and the breakdown items to which the budget information is associated are registered; 2. The administrative management system according to claim 1, wherein, in the execution stage, expenditure and income information for administrative data is registered for the subitems.

6. The detailed items include individual expenditure items, which are registered one or more times for each administrative data and correspond to budget item system items related to the lower-level budget items, and one or more accumulation items, which are registered one or more times for each individual expenditure item and correspond to budget information; The administrative management system according to claim 5, wherein, in the execution stage, the expenditure and income information is registered for the individual expenditure items.

7. 7. The administrative management system according to claim 5 or 6, which tally up one or more of the number of administrative data items, the number of itemized items, budget information linked to the administrative data, and expenditure / revenue information linked to the administrative data.

8. An administrative management method for managing administrative data, comprising: a computer stores administrative data having a plurality of types of data items, 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; An administrative management method which accepts a display request from a user terminal, determines the data items to be displayed based on the attribute-specific data item set corresponding to the attributes of the user who made the display request and / or the stage-specific data item set corresponding to the stage in the administrative activity of the user who made the display request, and processes the display.

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

Images