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 projects are conducted from a micro perspective, and that the two are not linked. This technology makes it possible to maintain consistency between individual plans and overall strategies by establishing rules, making the creation of revenue and expenditure plans for individual administrative projects more detailed and computerizing them, 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. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2005-293321 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 technology for efficiently promoting administrative activities in administrative organizations. [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 the 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 linkage of 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] Administrative data includes data items related to system items defined as master data in a multi-level tree structure, An administrative management system described in [1] or [2] that aggregates the number of administrative data items, the number of detailed items contained 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] storing a set of data items for each form, which is a set of the data items required for each form 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 the 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; An administrative management system according to any one of [1] to [4], which registers expenditure and income information for administrative data for the above-mentioned breakdown items during the execution stage. [6] The breakdown 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 described in [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 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, 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 that 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 of [1] makes it possible to present administrative data according to the attributes of users, thereby promoting administrative activities 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 of [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 of [4] makes it possible to determine the data items to be output depending on the type of report, thereby efficiently promoting administrative activities.

[0012] The invention of [5] makes it possible to associate 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 of the present invention allows for efficient budget execution by matching expenditures to individual expense items.

[0014] The invention of [7] makes it possible to efficiently grasp progress, particularly during the execution stage. [Effects 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 explanation of the drawings]

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

[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 accompanying drawings. Note that the following embodiment is an example of the present invention, and the present invention is not limited to the following embodiment, 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 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, public organizations, etc., such as the national 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, measures, and administrative projects. For example, it may be divided into four or more layers, such as by establishing a layer of sub-measures between measures and administrative projects, and administrative projects may be managed. A policy is a large set of administrative activities aimed at realizing basic guidelines for addressing specific administrative issues, and indicates the direction and objectives of urban development in the established administrative division (city, ward, town, village, etc.). A policy is a set of administrative activities based on the basic principles of a policy and aimed at realizing a specific policy, and indicates the measures and countermeasures 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 belonging to an administrative division based on the budget of that bureau. In this embodiment, the issue 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 procedures related to tasks and projects.

[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, plenary session and committee responses prepared by executive agencies such as administrative agencies in response to questions from assembly members, the planning, execution, and evaluation stages of administrative tasks and projects, and issues collected by assemblies and committees and used 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> An example of the flow of administrative activities in a local government will be explained. First, in the planning stage, plans for the tasks and projects to be implemented in the next fiscal 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 fiscal year are prepared, the budget requests are assessed, a budget proposal is prepared, and it is submitted to the assembly. Then, once the fiscal year begins, in the execution stage, the budget is executed for the tasks and projects approved by the assembly. In the evaluation stage, administrative evaluation reports are prepared for the 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 objective. One or more topics can be defined for each type of administrative object. In this embodiment, for example, when an administrative project is the objective, multiple divisions arranged chronologically, such as "budget preparation > request," "budget preparation > assessment," "budget preparation > preliminary announcement," "budget preparation > resolution," "budget execution," "settlement," and "administrative evaluation," are defined as topics. The above is just one example, and different divisions, abstract divisions, detailed divisions, etc. may also be defined. Furthermore, topic subdivision may be achieved by hierarchizing topics into multiple layers. For example, instead of the topic "Budget Compilation > XX," categories such as "Initial Budget Compilation (hereinafter referred to as "Initial") > XX" and "Supplementary Budget Compilation (hereinafter referred to as "Supplementary") > XX" may be defined, or subtopics of "Initial Budget > XX" and "Supplementary Budget > XX" may be defined in layers below "Budget Compilation." Furthermore, multiple categories arranged chronologically may also be defined as topics in lower layers. For example, categories such as "Request," "Assessment," "Unofficial Notice," and "Voting" may be defined in layers 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 for a certain topic can be understood as smaller stages of administrative activities related to that topic.

[0025] Data items are various data registered and managed regarding administrative objects. The required data items are categories of data items that must be registered. An optional data item is a category of data item for which the attribute name is predefined and which allows the input of data values ​​and the display of input data items by enabling or disabling them. The additional data item is a category of data item that allows you to register a unique attribute name, input data values, and display the input data items.

[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 comprises, 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 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, civil engineering departments (bureaus and sections), agriculture, forestry, and fisheries departments (bureaus and sections), and users and supervisors of original bureaus and original sections (section chiefs, department heads, etc.). 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 a 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, 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 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 configured with 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 configured with 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 accessible via a communication network NW including 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] 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 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 "registering") 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 and 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 organization information and department information as organizational structure items. The organization 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.) 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 administrative projects, 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. It may also be possible to define a user group, which is a collection of one or more users. The user group information may be predefined, for example, by the user group's identification information (user group ID) and the identification information of the users belonging to the user group, or users who have common attributes such as organizational structure items may be treated as a user group. Users to be included in a predefined user group may be arbitrarily selected, or may be selectable from user groups that have common attributes. 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 for the policy / program (policy ID / program ID), policy number / program number, policy name / program name, responsible department (department, section, office, etc.), policy purpose / program purpose, and policy summary / program summary. Furthermore, the program information includes identification information for 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 local government financial situation survey item system, budget subject system items that represent the tree-structured budget subject system by linking data items, and local government financial situation survey items that represent the tree-structured local government financial situation survey item system 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 for the budget item (budget item ID), identification information for the higher-level budget item to which the budget item belongs (budget item ID), budget item type (in this embodiment, either a sub-item or sub-item), and budget item name. The budget item type includes sub-items (higher-level budget items), which are higher-level items corresponding to the purpose at the time of settlement, and sub-items (lower-level budget items), which are lower-level items corresponding to the nature. 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. Expenditure breakdown purpose indicates the purpose of expenditure linked to administrative projects and is used for local government financial situation surveys in the settlement topic. Expenditure breakdown purpose information includes identification information for the expenditure breakdown purpose (expenditure breakdown purpose ID), identification information for the higher-level expenditure breakdown purpose to which the expenditure breakdown purpose belongs (expenditure breakdown purpose ID), identification information for the corresponding budget item (any of the sub-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] 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 that must 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 accordance with the higher-level policy and measure system. In this embodiment, the administrative goal master stores administrative goal information as an administrative goal system item. 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, etc.

[0043] <3.3. Registration of business information> 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 and item / subdivision details (budget subject system items) that are used at the time of execution and to which the expenditure amount is associated, and the expenditure breakdown purpose and budget nature (local government financial situation survey items) that are used at the time of settlement and to prepare the local government financial situation 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 use of the budget, and budget funding sources. As a breakdown item, 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, to which a sub-section (budget item system item) is associated. An individual expenditure item includes an accumulation item that indicates the budget amount, etc., and a breakdown of the funding source that indicates the funding source. Furthermore, individual tasks, projects, subprojects, 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 and projects 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 budget item category items (higher-level budget items) related to sub-items, and individual expense items, which are the breakdown items, are linked to budget item category items (lower-level budget items) related to sub-items. Furthermore, in any topic, labels indicating their contents may be assigned to individual tasks, projects, subprojects, or individual expense items. In this embodiment, a label indicating that a task or project is a priority project is assigned to a task or project, and a label indicating that a project is 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 business and project information is administrative data related to each business and project, and is registered for each execution year. In this embodiment, the business and project information includes basic information related to the business and project (basic business information), administrative goal information, budget information, financial resource information, and expenditure and income information related to the business and project. Basic information on administrative projects (basic information on administrative projects) is information on the content of administrative projects, and includes basic information (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 administrative project, revenue amount for administrative project, budget name, affiliated department / agency (organization system item), responsible department (organization system item), accounting category, administrative project status. It includes the status of the project (for example, "new," "expansion," "reduction," "suspended," "abolished"), item (higher-level budget item: budget item system item), major, medium, and minor classifications of expenditure breakdown purposes (local government financial situation survey items), expense classification, budget amount for the project, etc., and also includes optional items such as the purpose of the project, outline of the project, legal basis, 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, etc., as well as various other information related to the project.

[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 subject system items), as well as major, medium, minor, and detailed classifications of budget characteristics (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 piece of business information is configured to be able to hold the budget amounts for each stage for each individual expense item it has. The 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 details (budget item system items). For example, like the budget amount, the revenue amount is also linked to each topic, 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, and the revenue forecast amount, which is the amount of revenue forecast.

[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 > estimated item). Administrative projects have a structure that includes one or more minor projects, and minor projects include 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 estimated items are included in individual expense items, and are registered using estimated item information that indicates the budget amount for the administrative project or a higher-level breakdown item by being accumulated. Funding breakdowns are included as 0 or 1 in individual expense items, and are registered using funding breakdown information that indicates the revenue amount for the administrative project or a higher-level breakdown item.

[0048] The sub-project information includes various information related to the sub-project, such as the identification information of the sub-project (sub-project ID), the identification information of the 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 of the sub-project.

[0049] Individual expenditure items indicate expenditure items required for administrative activities related to the corresponding minor project, and individual expenditure item information includes identification information for the individual expenditure item (individual expenditure item ID), identification information for the related minor project (minor project ID), individual expenditure item name, budget amount for the individual expenditure item, individual expenditure item group label, individual expenditure item summary, sub-subdivisions (sub-budget items: budget item system items), and nature (budget nature: local government financial situation survey items). An accumulation item is a specific individual expense item included in an individual expense item, and accumulation item information includes identification information of the accumulation item (accumulation item ID), identification information of the related individual expense item (individual expense item ID), accumulation item name, budget amount for each topic, planned execution quarter, accumulation item overview, and accumulation basis (formula, etc.). The funding breakdown indicates the funding source for each individual expenditure item, and the funding information includes the identification information of the funding source (funding source ID), the identification information of the related individual expenditure item (individual expenditure item ID), the name of the funding source, the amount of revenue for each topic, the funding allocation rate, funding classification, item subsection details (budget item: budget item system item), responsible department (organization system item), allocation basis, and allocation reason. In this embodiment, a breakdown of specific financial resources is registered as financial resource information, and if the entire budget amount for one individual expenditure item information is covered by general financial resources, no financial resource information is registered, but if the amount is covered by specific financial resources, or specific financial resources and general financial resources, one piece of financial resource information is registered. The breakdown of general financial resources can be 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 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, 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 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 Department 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 Department 23> The issue management unit 23 registers issues associated with administrative tasks, 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 task 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 start a workflow.

[0054] Issue information includes the issue's identification information (issue ID), the corresponding administrative object's identification information (task / project ID), the issue's title and content, the person in charge, the issue creator, the issue status, the deadline, attachments, work items, and the issue group's identification information (issue group ID). For example, when executing a budget compilation workflow, an issue (issue group) for the "Budget compilation > Request" topic (registering task / project information for the initial budget request) is assigned to users in each original bureau and original division, and issues such as the "Budget compilation > Assessment" and "Budget compilation > Preliminary announcement" topics are assigned to users and heads of the Cabinet 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 notification regarding the issue displays the information regarding the issue issued to them 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 sends it to the administrative data management unit 21.

[0057] <3.6. Executing Workflows> For a specific topic, multiple issues are registered that are executed in stages, and the workflow is completed when the series of issues is completed. When performing administrative activities for multiple administrative projects or minor projects (administrative object groups), a set of issues (issue groups) 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 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 can 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 cannot 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 assessments can input assessment information, but cannot input request information.

[0060] <3.7. Reference to budgeted business information> There are two types of administrative and project information: information on new administrative and project projects and information on administrative and project projects that have been budgeted or canceled. More specifically, this information includes (1) administrative and project information for initial budget requests for new administrative and project projects (initial new), (2) administrative and project information for initial budget requests for administrative and project projects that were budgeted in the previous year (initial continuing), (3) administrative and project information for initial budget requests for administrative and project projects that are implemented every one or several years (initial biennial), and (4) administrative and project information for supplementary budgets that are requested after the budgets for these projects 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 carry out the issue.

[0062] (2) When registering administrative business information (initial continuation), the administrative data management unit 21 copies the data items of administrative business information related to each administrative business budgeted for the previous year at the start of the workflow or in a topic before the "Budget Preparation > Request" topic, and registers the administrative business information (initial continuation).The administrative data management unit 21 then accepts input, editing, and deletion of data items related to administrative businesses budgeted for the previous year, and updates the administrative business information (initial continuation).The issue management unit 23 accepts the completion operation of the administrative 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, copies 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).Then, it 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 administrative business information (corrections) registration from the person in charge of the issue, and requests 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 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 of the process of registering administrative and business information (correction) for a supplementary budget request. When newly registering administrative and business information (June 2023 correction) for a June supplementary budget request for administrative and business 1 for fiscal year 2023, the administrative data management unit 21 references the administrative and business information (initial fiscal year 2023) related to the initial budget recorded for administrative and business 1 for fiscal year 2023. As shown in the illustrated example, the administrative and business information (initial fiscal year 2023) includes various data items in the administrative and business layer related to administrative and business 1, various data items in the sub-business layer 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 the accumulation item A11 and funding breakdown A12 included in individual expense item A1, the accumulation item A21 and funding breakdown A22 included in individual expense item A2, and the accumulation item B11 and 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] Figure 3(b) is a conceptual diagram of when registering administrative business information (initial continuation). When newly registering administrative business information (initial continuation of fiscal year 2024) related to administrative business 1 for the current fiscal year (fiscal year 2024), the administrative data management unit 21 references administrative business information (initial fiscal year 2023) related to administrative business 1 for the previous fiscal year (fiscal year 2023), as well as administrative business information (June supplementary budget for fiscal year 2023) related 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 accumulated 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 various data items in the detailed project layer, the various data items in the individual expense item layer related to individual expense items A2 and B1, the accumulated items A11, A21, B11 included in the individual expense items A1, A2, B1, and the funding breakdown A12, A22, B12 will be duplicated to newly register administrative project information related to administrative project 1 (continued from the beginning of fiscal year 2024), and the administrative project information related to administrative project 1 (continued from the beginning of fiscal year 2024) will be accepted from users to update. 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> Figure 4 is a diagram showing an example of the connection between administrative and business information. In this embodiment, administrative and business information for each fiscal year is associated using a reference structure such as that shown in Figure 4. When an administrative or business continues, administrative and business operations of a continuing group of people can be grouped together by using a common administrative or business ID. Furthermore, administrative and business operations for each fiscal year can be uniquely distinguished by combining the administrative or business ID with a character string indicating the execution year. When multiple administrative and business information for each initial correction category is registered in the same execution year, as in this embodiment, administrative and business operations 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 and projects 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 carried out 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, input of data items related to business and project 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 receives a request to display the registration screen from the user terminal 3 and displays the registration screen. The registration screen W3 has 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 is 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 same fiscal year are duplicated and displayed in a preset state in each input field so that they can be edited, deleted, etc. Furthermore, when the item (budget item system item) of an administrative project is entered, 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 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, 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 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. Administrative business information viewing screen> Next, the browsing of data items related to the business and operation 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 the multiple users and / or user groups who have been granted viewing authority for the administrative data. Note that viewing authority information may also be set for an issue to grant the viewing authority. In addition, in this embodiment, the viewing authority information is described as being stored in the viewing authority master, but the data structure may be such that each administrative data item or issue includes the viewing authority information.

[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. In addition to or instead of the data item set defined according to user attributes, the display processing unit 27 may also 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.

[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 administrative objects, business status, issue status, workflow stage, 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 a 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 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 special-class users (such as the head of a local government) who are higher-ranking approvers in the workflow can be more macroscopic than the information 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 is an example of a display screen W7 for viewing registered business information. When a user requests the display of business information, the display processing unit 27 displays the 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 the business on the viewing screen W7, which displays the information on the business layer corresponding to the display axis and the 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). In addition, by pressing Add Difference on the viewing screen W7, a difference screen W8 is displayed for viewing the registered business information side by side.

[0081] <4.2. Difference screen for business information> Figure 8 is an example of the differential screen W8. When a user requests 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 or business designated by the user on the viewing screen W7, displays 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 in both display frames includes at least some common data items (e.g., required data items), so that 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 even 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 are, 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 specifying the display axis on the viewing screen W7 and the difference screen W8. However, instead of or in addition to specifying the display axis, 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 the display axis on the timeline. The illustrated example illustrates a case where display axes are specified for the comparison source and comparison destination when displaying differences. However, a similar screen display may also be used when specifying individual display axes. 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 alongside the difference screen W8 (viewing screen W7), for example, or may be configured to 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 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 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 the breakdown items of the budget to be executed, the names of the expenditure and income items, the 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 tallying unit 26 tally the number of tasks, projects, or sub-items, and / or one or more of the budget information, financial resource information, and expenditure / revenue information associated with each task. For example, on a search screen for tasks (not shown), the system tally the estimated items and financial resource details of tasks (sub-projects) searched for using predetermined tallying axes and conditions on the task search screen (not shown), and the display unit 27 displays the tallying results. The tallying axes are, for example, the execution year, budget type, status, and topic. The conditions may include, for example, one or more of the following 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 or not the project is a priority project (priority project label). This allows for the tallying of the number of tasks, 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 expenditure 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] <Embodiment 2> Next, a case where various forms relating 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.

[0091] <6.1.Database> The database DB according to this embodiment stores organization master, user master, policy and 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> Data item sets defined according to the output contents of various forms are called "form-specific data item sets." 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 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 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 and 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. [Explanation of symbols]

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

Claims

1. A subject master is provided that stores a one-to-multiple correspondence between at least some of the budget subject system items and the local government financial status survey items; On the administrative data registration screen with multiple data items, In response to input of the budget item system item related to the administrative data, refer to the item master, identify a local government financial situation survey item corresponding to the input budget item system item, and insert a value into a data item field corresponding to the identified local government financial situation survey item; When the budget item system item is input on the registration screen, a plurality of the local government financial situation survey items are filtered and presented, On the registration screen, the data items including the budget amount, the budget item system items, and the local government financial situation survey items are registered in association with the administrative data; The budget item system includes sub-items, An administrative management system in which the local government financial situation survey items include budget characteristics set under the sub-items.

2. The item master stores the correspondence between the sub-items and the budget characteristics, An administrative management system as described in claim 1, wherein, in the registration screen, in response to input of the section or item related to the administrative data, the subject master is referenced, the budget nature corresponding to the input section or item is identified, and a value is inserted into the data item column corresponding to the identified budget nature.

3. 3. The administrative management system according to claim 1, wherein when the budget subject system items are input on the registration screen, some or all of the local government financial situation survey items are automatically inserted into the data item column.

4. storing a set of data items by stage defined according to the stage of administrative activities; An administrative management system as described in claim 1 or claim 2, wherein on the registration screen, the data items of the administrative data are displayed and processed based on the stage-specific data item set at the budget preparation stage, and the data items including the budget amount, the budget subject system items, and the local government financial situation survey items are registered in correspondence with the administrative data.

5. 5. An administrative management system as described in claim 4, wherein the registration screen accepts the designation of the budget subject system items and / or the local government financial situation survey items that have been registered at the budget preparation stage, and registers expenditure and income information compiled based on the local government financial situation survey items.

6. The computer stores, as an item master, a correspondence relationship in which at least some of the budget item system items and the local government financial situation survey items are combined one to multiple times; On the administrative data registration screen with multiple data items, In response to input of the budget item system item related to the administrative data, refer to the item master, identify a local government financial situation survey item corresponding to the input budget item system item, and insert a value into a data item field corresponding to the identified local government financial situation survey item; When the budget item system item is input on the registration screen, a plurality of the local government financial situation survey items are filtered and presented, On the registration screen, the data items including the budget amount, the budget item system items, and the local government financial situation survey items are registered in association with the administrative data; The budget item system includes sub-items, An administrative management method in which the local government financial situation survey items include budget characteristics set under the sub-items.

7. A computer program that causes a computer to execute the administrative management method described in claim 6.

Images