Organizational chart creation program, organizational chart creation system, and organizational chart creation method

Abstract

When creating an organizational chart on a computer and outputting accounting information for each department or organization, the information is output based on projects (contracted construction work). [Solution] The organizational chart creation system 1 creates an organizational chart on the workspace that shows nodes representing departments and the relationships between those nodes. The department information represented by the nodes is associated with project information and accounting information. Since accounting information can be output even for projects that span multiple departments, it is possible to simulate the organization for each project and output accounting information and other data for that organization.

Description

Technical Field

[0001] The present invention relates to an organization chart creation program, an organization chart creation system, and an organization chart creation method. [[ID=']]

Background Art

[0002] Due to the need for business management in organizations such as companies, there is a need for software that can create an organization chart on a computer to show departments within the organization and their correlations.

[0003] For example, software that simulates organization charts before and after personnel transfers is disclosed.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Patent Document 2

[0005] [[ID=3']]

[0006] Patent Document 1 discloses a department hierarchy editing method characterized by cutting out a part of an organization chart, combining one or more of them, registering, displaying, and editing them as a project organization chart separately from the original organization chart.

[0007] However, when there is a new project (such as an ordered construction project) in the construction industry or the like, a part of the company organization, for example, the construction department and the sales department that are optimal for the ordered construction project, may be cut out to create a new group, and the project may be tackled by that group.

[0008] In such cases, instead of a permanent organizational restructuring, it is necessary to conduct simulations with new groups for each project. In this case, it is also necessary to record information (such as accounting information) for each project and department, and use this information for subsequent simulations.

[0009] In particular, when there are multiple cross-departmental projects, that is, projects involving collaboration between several departments, and the information of these departments, projects, and accounting records is not interconnected, it becomes difficult to evaluate the results of the projects performed by the departments involved. For example, it becomes difficult to simulate which combination of departments would be best for similar projects.

[0010] The cited literature does not mention that accounting information is linked to each project and each department. [Overview of the project] [Problems that the invention aims to solve]

[0011] The problem we are trying to solve is that when creating an organizational chart on a computer and outputting accounting information for each department or organization, the department or organization, project information, and accounting information are not interconnected. For example, it is not possible to simulate a department or organization based on project information (contracted construction information) and output accounting information. At the same time, this also addresses the issue of improving the usability of the user interface to facilitate the smooth output of information. [Means for solving the problem]

[0012] The present invention creates an organizational chart on a workspace that shows nodes representing departments and the relationships between those nodes, and its most important feature is that the departmental information represented by the nodes is associated with project information and accounting information.

[0013] This invention has been made in view of the above problems, and employs, for example, the following means. In other words, a computer, Organization information acquisition means for acquiring organizational information that includes the organization's organizational code or organizational name as organizational identification information. A means for acquiring departmental information that includes the department code or department name of a department constituting the aforementioned organization as departmental identification information. Project information acquisition means for acquiring project information that includes the project code or project name of a project in which the aforementioned department is involved as project identification information. A project accounting information acquisition means for acquiring the accounting information of the aforementioned project, A node addition means that adds a new node by a user's node addition operation, which is performed by specifying a node that corresponds to the department and is already installed in the workspace displayed on the computer's display unit. Node relationship drawing means for representing the relationship between the already placed nodes and the new nodes on the workspace, Node organizational diagram storage means for storing the organizational diagram represented by the aforementioned nodes in a storage unit, Organizational chart identification means for associating the organizational chart with organizational identification information, An organizational chart reading and display means that accepts input of organizational identification information and displays the corresponding organizational chart in the workspace, and A department / project-specific accounting information output means that outputs accounting information for the project in the department, based on the department identification information and the project identification information. The present invention provides an organizational chart creation program characterized by its function as such. [Effects of the Invention]

[0014] The organizational chart creation program of the present invention uses a computer, Node organization chart storage means for storing the relationships between nodes showing the organization chart in the storage unit, department-specific accounting information acquisition means for acquiring accounting information of departments, and for each project related to the individual projects in which the department is involved, functioning as department-specific project information acquisition means for acquiring project information including at least a code unique to the project and a project name, there is an advantage that the organization is simulated for each project and the accounting information can be linked. In addition, since nodes can be added and deleted by the operation of the user performed by specifying a node, there is an advantage that the operability of the user is improved.

Brief Description of Drawings

[0015] [Figure 1] It is a diagram showing an interface for creating an organization chart in the organization chart creation system 1. [Figure 2] It is a diagram showing a screen for inputting the output conditions of forms. [Figure 3] It is a diagram showing an example of the form being output. [Figure 4] It is a diagram showing a menu screen. [Figure 5] Diagram showing an operation of inputting organization information on the extended organization chart creation screen [Figure 6] It is a diagram showing an operation of newly creating a node on the extended organization chart creation screen. [Figure 7] It is a diagram showing an operation of setting the core organization on the extended organization chart creation screen. [Figure 8] It is a diagram showing an operation for adding or deleting nodes etc. on the extended organization chart creation screen. [Figure 9] It is a diagram showing an operation of adding a node of a new department on the extended organization chart creation screen. [Figure 10] It is a diagram showing an operation of adding a node of an existing department on the extended organization chart creation screen. [Figure 11] It is a diagram showing a department search screen. [Figure 12]This diagram shows the organizational chart display section after existing department nodes have been added to the extended organizational chart creation screen. [Figure 13] This diagram shows the organizational chart display when a new department node is added under the company-wide node in the extended organizational chart creation screen. [Figure 14] This figure shows the extended organizational chart creation screen after entering organizational information. [Figure 15] This is a diagram showing the organization search screen. [Figure 16] This diagram shows the organizational chart display area after an existing organizational chart has been added to the extended organizational chart creation screen. [Figure 17] This is a diagram showing the registration screen for ordered construction projects. [Figure 18] This diagram shows the invoice information input screen (for one department). [Figure 19] This diagram shows the input screen for report output conditions (breakdown of uncompleted construction expenditures, no department code specified). [Figure 20] This is a diagram of the output report (Breakdown of Expenditures for Uncompleted Construction Work - Osaka Head Office). [Figure 21] This is a diagram showing the output report (Breakdown of Expenditures for Uncompleted Construction Work - Tokyo Branch). [Figure 22] This is a diagram showing the overall structure of the extended tissue. [Figure 23] This diagram shows the voucher information entry screen (multi-departmental). [Figure 24] This diagram shows the input screen for report output conditions (breakdown of uncompleted construction expenditures, with department code specification). [Figure 25] This is a diagram showing the output report (Breakdown of Expenditures for Uncompleted Construction Work - Building Department Hierarchy). [Figure 26] This diagram shows the input screen for report output conditions (list of ordered construction projects). [Figure 27] This is a diagram showing the output report (list of ordered construction projects). [Figure 28] This diagram shows the input screen for report output conditions (project profit trend table). [Figure 29] This is a diagram showing the output report (projected profit trend table). [Figure 30]This diagram shows the input screen for report output conditions (project-specific profit and loss management table). [Figure 31] This diagram shows the output report (profit and loss management table by project). [Figure 32] This is a diagram showing the construction inquiry screen. [Figure 33] This is a flowchart showing the organizational chart drawing process. [Figure 34] This is a diagram (network diagram) showing an overview of the organizational chart creation system 1 of this embodiment. [Figure 35] This is a hardware configuration diagram for server 10. [Figure 36] This is a hardware configuration diagram of user terminal 20. [Modes for carrying out the invention]

[0016] Embodiments of the present invention will be described with reference to the drawings. In the following embodiments, the same or corresponding parts may be denoted by the same reference numerals, and their descriptions may be omitted as appropriate. Furthermore, the drawings used below are for illustrative purposes only and may differ from the actual device configuration, user interface (UI), data structure, etc.

[0017] (Summary of the embodiment) The outline of this embodiment will be described with reference to the drawings (Figures 1 to 3). In the following, the system that performs processing using the organizational chart creation program P1 of this embodiment will be referred to as the organizational chart creation system 1. Furthermore, in the following explanation, construction work (contracted construction work) will be used as an example of a project. A project encompasses construction work, and the term "project" can be replaced with "construction work." For example, the construction code described later is an example of a project code, and the construction master is an example of a project master. Figure 1 shows the interface for creating an organizational chart in the organizational chart creation system 1. In the organizational chart creation system 1, the processor 122 of the server 10 displays a user interface (extended organizational chart creation screen, described later) on the user terminal 20 as shown in Figure 1. Users can create organizational charts within the workspace of this user interface (organizational chart display section, described later). In Figure 1, the "Architectural Department Hierarchy" and the "Civil Engineering Department Hierarchy" are virtual departments. In this user interface, the processor 122 displays an organizational chart code for identifying the organizational chart, as well as department codes and department names. Figure 2 shows the screen for entering the output conditions for a report. The processor 122 displays a user interface (report output condition input screen, described later) on the user terminal 20, as shown in Figure 2. On the displayed screen, users enter information related to their organization, such as the organization code and department code, as well as output conditions for reports, such as the date and project code. Figure 3 shows an example of a printed report. The processor 122 obtains the output conditions for the report and causes the output unit 284 to output a report that meets those output conditions. In other words, users can create new organizational charts (extended organizational charts) within the workspace and generate accounting reports for the new departments created in those extended organizational charts. As will be explained in more detail later, one advantage is that accounting reports can be generated for each project in which the extended organization is involved. For example, it is possible to input the construction and sales departments for each project, and then collect the projects received by each department, which has the advantage of allowing you to aggregate the order amount, cost, and profit for each department.

[0018] (Details of the embodiment) The organizational chart creation system 1 according to this embodiment will be described in detail below. Organizational chart creation system 1 includes a computer (server 10) equipped with an organizational chart creation program P1, and provides a system for users to create organizational charts on their user terminals. In other words, the organizational chart creation system 1 is a system in which the information processing performed by the organizational chart creation program P1 is concretely realized using hardware resources. The following describes, in order, the components that make up Organizational Chart Creation System 1: 1. User Interface, 2. Program Processing, 3. Data, and 4. Hardware Configuration.

[0019] (Definition of terms) Here, I will define some terms. "Accounting" refers to the recording, calculation, or management of the flow of money or goods (valuable items), or the procedures, mechanisms, or methods for clarifying the management status of an organization such as a company. However, it is not limited to the above, and in context, it may also include what the terms "finance" or "accounting" mean. "Accounting information" refers to information related to accounting. For example, this includes information entered into vouchers or information output in reports. For information entered into vouchers or information output in reports in this embodiment, please refer to sections 1. User Interface and 3. Data. The contract amount information, construction period information, cost information, sales information, and profit information are, respectively, information on the contract amount, construction period, cost information, sales information, and profit information, but the specific content of each piece of information may differ depending on the type of report to be output. For example, in this embodiment, the profit information in the project-specific profit and loss management table includes profit up to the previous period and profit incurred in the current period. On the other hand, the profit information in the project project profit trend table includes profit at the estimated cost stage as well as profit at the final projected profit amount. For details, please refer to section 1. User Interface, etc. An "organization" is a group of people working together to achieve a certain purpose, such as a company, a sole proprietorship, or a group. In the following, the term "organization" may be used to refer to a collection of "departments," which will be discussed later. "Organization name" refers to the name of the organization. Specifically in this embodiment, this may be the organization's official name, its name in kana, or its abbreviation. Similarly, the terms "department name," "project name," and "document name" used below refer to the names of the department, project, and document, respectively. A "department" is a division of an organization. It can also be described as a constituent unit of the organization. The terminology varies depending on the organization, and may include department, section, bureau, group, or unit. For example, a "section" may be a subordinate department to a "department," and there may be a hierarchical structure where different departments are located below a certain department. An "extended organization" is a new organizational unit distinct from an existing organization. It can also be described as a collection of departments different from the collection of departments that make up an existing organization. Organizational chart creation system 1 can simulate a new organization and create an organizational chart. Although the term "extended" is used, it does not have to be an extension or expansion of an existing organization; it can be an entirely new organization. A "workspace" is the workspace that a computer (processor) displays on its screen. A GUI (Graphical User Interface) allows users to operate it visually and intuitively. A "node" is an object on the workspace that represents a specific subject. In this embodiment, departments are represented by nodes. A "user" is anyone who uses the organizational chart creation system 1. This includes both individuals and corporations. For simplicity, employees (staff) belonging to an organization (company) that is a user may also be referred to as users without distinction. However, for the sake of explanation, those who manage the system may be called administrators, and all other users may be called general users. Users are usually general users. A "project" is a set of activities or the entire plan for such activities that are planned and executed with a set deadline to achieve a specific objective (such as the completion of a building). In the following embodiments, a "project" is a "construction project." "Pressing down" refers to actions such as mouse clicks and taps, which are used for selection or confirmation.

[0020] In the following, when the term "○○ processing" is used, it means that the computer's processor executes processing based on the "○○" program stored in the program storage. The same word will be used in place of "○○" throughout this paragraph. In other words, the "○○" program is a program that makes the computer function as a "○○" means by executing the "○○" process. Furthermore, this means that the control unit equipped with the processor also functions as a "○○" unit (or "○○" device). In this case, the "○○" section means that it executes the "○○" process based on the "○○" program. Furthermore, the "○○" process may sometimes be described as the "○○" method, which involves multiple steps (or procedures) in chronological order.

[0021] For example, the organizational chart creation program P1 is a program that makes the computer function as an organizational chart creation means by executing the organizational chart creation process. In this case, the control unit 12 of the computer equipped with the processor 122 functions as an organizational chart creation unit (or organizational chart creation device). Furthermore, the organizational chart creation program P1 works in conjunction with the hardware to provide a method for creating organizational charts.

[0022] In the organizational chart creation system 1, each terminal (computer), such as the server 10 and user terminals 20, is equipped with a processor. However, when simply referring to a processor, it refers to the processor that performs processing using the organizational chart creation program P1, and in this embodiment, the processor 122 of the server 10.

[0023] On the other hand, if the organizational chart creation system 1 is completed entirely on the user terminal 20 without using a network, the processor shall refer to the processor 222 of the user terminal 20. In this case, wherever "processor 122" is mentioned in the following explanation, it shall be read as "processor 222" unless there is a contradiction.

[0024] For simplicity, in the following, the action of "the processor 122 of server 10 receiving a request from a terminal and returning data for the terminal's output unit to output" may be described as "the processor 122 outputs to the terminal's output unit" or "the processor 122 outputs." For example, this could involve displaying an image on the terminal's display, displaying a web page in the terminal's browser, or outputting sound to the terminal's audio output unit (speaker). Similarly, the action of "the processor 122 of server 10 causing data to be stored in the data storage unit 14b of storage unit 14" may be described as "the processor stores (data)."

[0025] In other words, for simplicity, even if it can be determined that a processor such as the user terminal 20 will process something, it may be stated that the processor 122 will process it (or cause it to process).

[0026] 1. User Interface (UI) First, the interface that the organizational chart creation system 1 of this embodiment displays on the user terminal 20 will be explained using diagrams. The interface described below is a simplified version of the one that the processor 122 displays in the browser of the user terminal 20. The user's inputs into the user interface input fields, etc., can be retrieved by the server 10 (via the network).

[0027] Furthermore, only icons related to functions necessary for explanation will be displayed, and other publicly known icons will be omitted. For example, the back button for returning to the previously displayed page has been omitted. Furthermore, explanations of functions that are typically included in a UI may be omitted. For example, pressing a button icon may execute a predetermined process, or pressing a hyperlink may cause the communication control unit to access the URL embedded in that link.

[0028] Although not explained here, various operations can be undone (UNDO operation) using the UI described below. For example, if you accidentally delete a necessary node, you can undo the operation and return to the state before the deletion. Similarly, if you add an unnecessary node, you can undo the operation (without deleting it) and return to the state before the addition. The process performed by the processor at this time is called "cancel operation processing (such as canceling a node deletion operation or canceling a node addition operation)."

[0029] Figure 4 shows the menu screen. The user selects an item from the menu screen. For example, if they want to open a screen for entering information or a screen for generating a report, they select the corresponding item.

[0030] As shown in Figure 4(a), the menu screen includes a menu tab UI-11 and an item-specific menu UI-12. The menu tab UI-11 is a tab that categorizes items by type, and the item-specific menu UI-12 is an item that corresponds to the input and output of information. The processor 122 displays the item-specific menu UI-12 for each tab.

[0031] For example, when a user clicks "Department Registration" on the "Common" tab (Figure 4(a)), processor 122 displays the department registration screen (hereinafter referred to as the "Extended Organizational Chart Creation Screen") as described in the next section.

[0032] Figures 4(a) through 4(c) show the screens corresponding to the "Common" tab, the "Financial" tab, and the "Cost" tab, respectively.

[0033] Figure 5 shows the process of entering organizational information on the extended organizational chart creation screen. First, let's explain the Extended Organizational Chart Creation Screen. The Extended Organizational Chart Creation Screen is where users create and edit new organizational charts (hereinafter referred to as "Extended Organizational Charts"). Processor 122 displays the UI for creation, editing, etc., on the user terminal 20.

[0034] As shown in Figure 5, the extended organizational chart creation screen includes an organizational information input section UI-21, an organizational chart display section UI-22, a departmental information input section UI-23, and a function icon UI-24.

[0035] The organizational information input unit UI-21 is an input unit for entering information about the extended organizational chart. Specifically, you will need to enter the organization code (a 4-digit number) for the extended organizational chart, the effective date, the organization name, and the organization's name in kana.

[0036] As shown in Figure 5, in this embodiment, the user enters "0002" as the organization code, "April 1, 2017" as the start date, "Architecture and Civil Engineering Extended Organization" as the organization abbreviation, and "KENCHIKU-DOBOKUKAKUCHOUSOSIKI" (in half-width characters) as the organization name in kana. In the following, even if the actual input is in half-width characters, it will be written as full-width characters in the specification.

[0037] The organizational chart display unit UI-22 and the departmental information input unit UI-23 will be explained below with reference to the diagrams.

[0038] Function icon UI-24 is an icon that provides a function according to the displayed content. For example, when the user clicks the icon labeled "Save," processor 122 saves the data (such as input content). Similarly, "Browse" means to browse (read) the data, "Delete" means to delete the data, "Clear" means to clear the input content, and "Exit" means to end the input process. Explanations of well-known functions are omitted.

[0039] Although the function icons differ from screen to screen, for simplicity, they are all referred to as function icons (e.g., function icon UI-34 or function icon UI-44). Furthermore, in some cases (such as Figure 6), the function icons are omitted from the drawings if they are not relevant to the explanation.

[0040] In this embodiment, the organizational chart creation system 1 stores the organizational chart of the basic organization (basic organization) in the storage unit 14 (by a method similar to the method described below). The organizational chart of this basic organization is assigned the organizational code "0000," and it is possible to read (recall) this organizational chart of the basic organization. Further details will be provided later.

[0041] Figure 6 shows the operation of creating a new node in the extended organizational chart creation screen. When a user performs a predetermined operation on the organizational chart display unit UI-22 (right-click with the mouse in this embodiment), the processor 122 displays a "New" icon on the organizational chart display unit UI-22. When the user presses the icon, the processor 122 creates and displays nodes related to the core organization (nodes (icons) corresponding to departments) on the organizational chart display unit UI-22, as described in the next section.

[0042] Figure 7 shows the operation for setting the core organization in the extended organizational chart creation screen. By operating the icons described above, the processor 122 creates and displays nodes in the organizational chart display unit UI-22 that represent core departments.

[0043] Here, the department information input unit UI-23 is an input unit where the user enters information about the department. In this embodiment, the department information input unit UI-23 includes an input unit for inputting a four-digit department code, a department abbreviation, a department kana abbreviation, and the official name of the department.

[0044] In Figure 7, the user inputs the information of the core departments mentioned above into the department information input unit UI-23. Here, we have created a core organization called "Company-wide." Specifically, the department code is "0000," both the official department name and department abbreviation are "Company-wide," and the department kana abbreviation is "Zensha."

[0045] In this embodiment, the department code "0000" is a special code that does not have any subordinate departments when it is newly created. This is not a successor to the "Company-wide" (department code 0000) included in the basic organization (organization code 0000), but is a completely separate entity.

[0046] The processor 122 reflects the official department name and department code entered in the department information input unit UI-23 onto the nodes on the organizational chart display unit UI-22.

[0047] In the following, to distinguish between each node, nodes corresponding to departments will be represented as "Department Name + Node". For example, a node that supports the entire company will be called a "company-wide node."

[0048] Next, we will explain how to add nodes corresponding to departments.

[0049] Figure 8 shows the operations for adding or deleting nodes in the extended organizational chart creation screen. Upon receiving a user's specified operation, which involves specifying an already deployed node, the processor 122 adds, deletes, sorts, or moves the node.

[0050] In this embodiment, a predetermined range from the node is on the node. As shown in Figure 8, in this embodiment, when the user right-clicks on a node, the processor 122 displays options (add, delete, and sort) indicating what to do with that node.

[0051] When the user selects "Add" (referred to as the "(node) add operation"), the processor 122 adds a new node in association with the aforementioned node. When the user selects "delete" (referred to as "(node) deletion operation"), the processor 122 deletes the node. When the user selects "Sort" (referred to as the "(node) sort operation"), the processor 122 sorts the nodes (in order of department code) if there are multiple nodes. When the user selects "Move" (referred to as "(node) move operation"), the processor 122 moves the nodes if there are multiple nodes. Node movement is performed by the user via drag and drop, etc.

[0052] This section explains what happens when the user selects "Add".

[0053] Figure 9 shows the operation of adding a new department node in the extended organizational chart creation screen. As shown in Figure 9, when an additional operation is performed on the company-wide node, the processor 122 adds a new department node in a manner that associates it with the company-wide node, or in this embodiment, in a manner that associates it as a subordinate department of the company-wide node.

[0054] In the example in Figure 9, the department code for the new department is "1400" (a department code set by the user and not currently in use), and the official department name and department abbreviation (determined by the user here) are "Architectural Department Hierarchy".

[0055] Furthermore, processor 122 indicates that the (existing) company-wide nodes and the (added) building department hierarchy nodes are interconnected. The relationships between departments have a tree structure. In this embodiment, the processor 122 displays higher-level departments on the left side of the organizational chart display unit UI-22 and lower-level departments on the right side, and indents the lower-level departments (indents the text).

[0056] We've explained how to add a new department here, but next we'll explain how to add an existing department.

[0057] Figure 10 shows the operation of adding a node for an existing department in the extended organizational chart creation screen. This section explains how to add an existing department under the Architecture Department hierarchy node (as a subordinate department of the Architecture Department hierarchy node).

[0058] When a user enters department information, they can select and add departments included in the basic organization described above (and all departments under that department) by pressing the department search button UI-231 located at the far right of the "Department Code" field in the department information input section UI-23. This is explained below.

[0059] Figure 11 shows the department search screen. When the user presses the department search button UI-231, the processor 122 displays the department search screen. The department search screen includes a department search criteria input section UI-251, a department search button UI-252, a department search results list display section UI-253, and a confirmation button UI-254.

[0060] When a user enters search criteria into the department search criteria input section UI-251 and presses the department search button UI-252, the processor 122 displays a list of existing departments that match the search criteria in the department search result list display section UI-253.

[0061] In addition to the department (official department name or abbreviated department name) shown in Figure 11, other search criteria can include the department's abbreviated name in kana, department code, and organization code. The method of using the organization code as a search criterion will be described later.

[0062] As shown in Figure 11, the user selects "department abbreviation" as the search criterion and searches for department abbreviations that include "architecture" (partially matching the search term). The processor 122 then displays the corresponding departments in the department search results list display unit UI-253.

[0063] In this case, the processor 122 displays the department information in the department search results list display unit UI-253, namely the department code, department abbreviation, department kana abbreviation, and organization name (the organization name entered in the organization information input unit UI-21 of the extended organizational chart creation screen).

[0064] The user selects the department they want to add as a subordinate department to the aforementioned node (the Architecture Department hierarchy node) from the displayed existing departments, and then presses the confirm button UI-254. As shown in Figure 11, the processor 122 inverts the department selected by the user (in white text on a blue background).

[0065] This section explains the case where the user selects the Head Office Construction Department and presses the confirmation button UI-254, that is, when adding the Head Office Construction Department.

[0066] Figure 12 shows the organizational chart display section after existing department nodes have been added in the extended organizational chart creation screen. As shown in Figure 12, a Head Office Construction Department node has been added under the Construction Department hierarchical node in the organizational chart display unit UI-22.

[0067] When selecting or adding an existing organization, the user cannot change the contents of the department information input section UI-23 (processor 122 displays each input section of the department information input section UI-23 in gray). This is because departmental information of the base organization cannot be edited within the extended organization.

[0068] Figure 13 shows the organizational chart display when a new department node is added under the company-wide node in the extended organizational chart creation screen.

[0069] As described above, specifically by right-clicking on the company-wide node and adding a new node, a "Civil Engineering Department" hierarchy, distinct from the "Architecture Department" hierarchy, has been added as a subordinate department of the company-wide organization. This Civil Engineering Department is a new department that does not exist in the basic organizational structure, and its department code is "1500".

[0070] Next, we will describe a method for creating extended tissue using a method different from the one described above.

[0071] Figure 14 shows the extended organizational chart creation screen after organizational information has been entered (the diagram is the same as in Figure 5). This section explains how to load an already created organizational chart into the organizational chart display unit UI-22.

[0072] When the user presses the "Browse" button on the function icon UI-24, processor 122 displays the organization search screen.

[0073] Figure 15 shows the organization search screen. As shown in Figure 15, the organization search screen includes an organization search condition input section UI-261, an organization search button UI-262, an organization search result list display section UI-263, and a confirmation button UI-264.

[0074] When a user enters search criteria into the organization search criteria input unit UI-261 and presses the organization search button UI-262, the processor 122 displays the organization code stored in the memory unit 14 and the name of the organization associated with that organization code on the organization search result list display unit UI-253.

[0075] In this case, the processor 122 displays the organization information in the organization search result list display unit UI-263, namely the organization code, organization abbreviation, and organization kana abbreviation.

[0076] In the case shown in Figure 15, only the basic organization (organization code 0000) is stored, so only information related to that basic organization is displayed.

[0077] The user selects the organization from the displayed existing organizations whose data they want to retrieve and presses the confirmation button UI-264. This section explains the process when a user selects "2017 Basic Organization (Organization Code 0000)" and presses the confirmation button UI-254, i.e., when adding a basic organization.

[0078] Figure 16 shows the organizational chart display section after an existing organizational chart has been added to the extended organizational chart creation screen. As shown in Figure 16, the organizational chart of the basic organization is displayed in the organizational chart display unit UI-22. In the basic organizational structure of this embodiment, the entire company (department code 0000) has the Osaka Head Office (department code 0010) and the Tokyo Branch Office (department code 2000) as its direct subordinate departments.

[0079] Since the nodes displayed in the organizational chart display unit UI-22 can be modified, users can create new organizational charts based on the displayed organizational chart. For example, a "Legal Department" (not shown in Figure 16) could be added directly below the Osaka Head Office (not shown in Figure 16).

[0080] In this embodiment, hierarchical numbers are assigned sequentially from the top of the organizational chart (from left to right on the organizational chart display unit UI-22).

[0081] For example, in Figure 16, the entire company is represented as the first tier, the Osaka head office and Tokyo branch are the second tier, the head office general affairs department and head office construction sales department are the third tier, and the general affairs section and accounting section are the fourth tier. In the organizational chart, departments located deeper in the hierarchy are assigned higher tier numbers. As mentioned above, the organizational chart display unit UI-22 represents this hierarchy using steps (like indentations).

[0082] In this embodiment, the representation of hierarchy is not limited to numbers, but can also be expressed using organizational units, etc. For example, the first level can be "Company-wide," the second level "(Head Office) Branch," the third level "Department," and the fourth level "Section." This is because the database has a correspondence table between hierarchy and organizational units. For example, the storage unit 14 stores the hierarchy name "Department" associated with hierarchy "3".

[0083] Next, we will explain how to output reports related to a newly created department. First, I will explain how to register a construction project and enter the invoice. After that, I will explain how to output the reports.

[0084] Figure 17 shows the screen for registering ordered construction projects. Users register their projects on the project registration screen.

[0085] When the user clicks the "Register Ordered Work" item on the menu screen, the processor 122 displays the Ordered Work Registration screen (see Figure 4(c)). The processor 122 displays an input section on the order registration screen for entering various construction information.

[0086] As shown in Figure 17, the order registration screen includes a basic construction information input section UI-31, a construction information tab UI-32, a detailed construction information input section UI-33, and a function icon UI-34.

[0087] The UI-31 basic construction information input unit is an input unit for entering basic construction information such as the construction code and construction name. In this embodiment, the project code (and (project) sub-number if necessary), project name (such as project abbreviation), history number, order date, order registration date, completion category, completion accounting category, and common cost category are included. As will be explained in more detail later, for example, the history number is a management number for the change history.

[0088] The Construction Information tab UI-32 is a tab that categorizes items related to contracted construction projects by type. As shown in Figure 17, the construction information tab UI-32 includes tabs for basic information, contract information, workers' compensation information, billing information, investment information, individual housing information, construction manager information, extended information, and optional information. The processor 122 displays the UI-33 construction details input section for each of the aforementioned tabs.

[0089] The UI-33 construction details input unit is an input unit for entering detailed information related to construction work. As shown in Figure 17, the "Basic Information" tab includes the official name of the project, the department in charge of the project, the person in charge of the project, the sales department in charge, the sales person in charge, the type of project, information on the construction period (contract period and internal construction period), information on the site (site name, address, telephone number, etc.), project overview, memo, information on related parties such as agents, engineers, and designers, information on the order (order type, order category, and order method, etc.), and various categories (JV category, etc.).

[0090] Function icon UI-34 is the same as the function icon described above, so its explanation will be omitted. However, it provides different functions, and function icon UI-34 includes functions for attaching documents and printing (printing and previewing).

[0091] Next, I will explain how to enter data into the slips.

[0092] Figure 18 shows a screen for entering invoice information (one department). The user enters the invoice information on the invoice information entry screen.

[0093] When the user clicks the voucher entry item (in this case, transfer voucher entry) on the menu screen (see Figure 4(b)), the processor 122 displays the voucher entry screen. The processor 122 displays an input section on the slip information input screen for entering various types of slip information.

[0094] As shown in Figure 18, the voucher information input screen includes a basic voucher information input section UI-41, a voucher function icon UI-42, an accounting information input section UI-43, and a function icon UI-44.

[0095] In this embodiment, the basic information input unit UI-41 includes the invoice number (invoice No.), invoice date, history, invoice category, department, and business partner.

[0096] The invoice number is a unique number for each invoice and is assigned by the server 10 during input. In this embodiment, it consists of the year and month of the invoice date (6 digits) + a sequential number (4 digits).

[0097] The invoice date is the date the transaction occurred (the accounting reference date).

[0098] The history is the (update) history of the slips associated with the history number. The history number and the content of the history (date and time, etc.) are linked.

[0099] The department is the department that created the invoice. The case where the department is not entered will be discussed later.

[0100] The trading partner is the trading partner related to the invoice in question.

[0101] In this embodiment, the slip function icon UI-42 relates to the sorting dictionary, sorting dictionary registration, debit / credit reversal, tax-exclusive total display, consumption tax calculation, non-deductible consumption tax display, and (business partner) public information introduction, as indicated by their respective names. A detailed explanation is omitted.

[0102] As shown in Figure 18, the accounting information input unit UI-43 has input sections that are broadly divided into debit and credit sides, each equipped with input sections for (account) title, department, order number (No.), customer (and tax-exempt business (exempt)), project name (project), work type, expense item, sub-item, consumption tax category (consumption tax category), taxable category (taxable category), amount, and consumption tax amount (consumption tax).

[0103] The "Tax-Exempt Business" checkbox is used to indicate on a document transactions that fall under the category of "purchase transactions from a tax-exempt business" in accordance with the implementation of the invoice system.

[0104] "Work type" is a code that represents the classification of work processes in construction. Construction budgets and costs are managed at this level. Note that there are also codes for construction work types (for example, "general civil engineering," "general building construction," "roofing work," or "electrical work"), but these are separate from the work types.

[0105] "Tax classification" here refers to the consumption tax rate (for example, tax-exempt, reduced tax rate, or standard tax rate).

[0106] The accounting information input unit UI-43 includes a debit (credit) total unit UI-431, and the processor 122 calculates the sum of the amounts entered in the debit and credit fields and the consumption tax amount and displays it in the debit (credit) total unit UI-431.

[0107] Processor 122 obtains the amounts and accounts related to deposits, as well as the amounts and accounts related to withdrawals, and calculates accounting information such as profit. Publicly known techniques are used as appropriate for the processing related to the calculation of this accounting information.

[0108] Furthermore, as shown in the voucher information input screen, this accounting information is entered in association with projects and departments, so the processor 122 can output accounting information for each project or department.

[0109] Function icon UI-44 is the same as function icon UI-34 mentioned above, so its explanation will be omitted.

[0110] This concludes the input of construction information and accounting information (vouchers). This section explains how to output reports, particularly reports related to newly created organizations (extended organizations).

[0111] When the user clicks an item related to report output on the menu screen, the processor 122 displays the corresponding information input screen. In other words, the processor 122 displays an input section for inputting the information necessary for outputting the report. This section explains using an example such as a breakdown of expenditures for uncompleted construction work (see Figure 4(b)).

[0112] Figure 19 shows the input screen for report output conditions (breakdown of uncompleted construction expenditures, no department code specified). The report output conditions input screen is where users enter the conditions (report output conditions) for the reports they want to output. The processor 122 displays an input section on the report output condition input screen for the user to input the conditions for the report to be output.

[0113] As shown in Figure 19, the report output condition input screen includes a report type selection section UI-51, a report output condition input section UI-52, and a function icon UI-53.

[0114] Furthermore, on the report output condition input screen, processor 122 displays at the top which report is to be output (in Figure 19, it displays "0273: Breakdown of Expenditures for Uncompleted Construction Work").

[0115] The form type selection unit UI-51 is an input unit for selecting the type of form. In the example in Figure 19, there is an input field for selecting the report type, such as "Cost Management" or "Financial Management," from a dropdown menu. This allows selection when different formats are available for the same report, such as those with different order of items or different aggregation units.

[0116] The report type selection unit UI-51 of this embodiment includes options for "by construction department" and "by sales department," and the user can select one of these. These will be described later.

[0117] The report output condition input section UI-52 is an input section for inputting the output conditions for a report.

[0118] The report output condition input section UI-52 in Figure 19 includes an organization / department input field (labeled "Department Code" in Figure 19) for inputting the organization and department (organization identification information and department identification information), a cancellation status selection field (cancelled work), a completion category selection field (completion category), a completion accounting category selection field (completion accounting category), a work code input field (work code), a completed output field (completed output), a date input field (date), a tax category selection field (total amount), and an approval status selection field (processing target (approval)).

[0119] The organizational department input field includes an organizational code input field, a hierarchy (selection) input field, and a department code input field. The user enters the organizational code of the department to which the report should be generated, the hierarchy (such as a branch office), and the range of department codes in the organizational department input field. However, it is not necessary to fill in all input fields, and some items may be left blank. In this embodiment, items that are left blank will be treated as "not selected" (all selected).

[0120] The fields for selecting whether a project has been cancelled, whether it has been completed, and whether it has been completed are filtering criteria based on the status of the project, but we will omit further explanation.

[0121] The construction code input field is provided. The user inputs the range of construction codes for which the report should be generated. In this embodiment, the construction codes are numbered by date and sequential number.

[0122] The completed work output section includes an input field for specifying and entering the completion date for completed construction work. The user enters the range of completion dates for the construction work for which the report will be generated.

[0123] The date input field is used to enter the date range for the vouchers to be included in the calculation. This section focuses on aggregating information from vouchers that record the costs incurred during construction (vouchers entered under the "Work in Progress" account). The user enters the date range for the report to be generated.

[0124] The tax category selection field includes input fields for selecting either the tax-inclusive amount or the tax-exclusive amount, and the user selects one of these options.

[0125] The approval status selection field includes an input field to choose whether to include only documents that have been registered / submitted and approved in the workflow (select "Approved Only" if only approved documents are included), and the user selects one of these options.

[0126] Function icon UI-53 is the same as the function icon described above, so its explanation will be omitted. However, the functions offered differ; function icon UI-53 includes features related to PDF output or CSV output, among others.

[0127] After entering the report output conditions, the user selects the command from the function icon UI-53. For example, when a user presses the "Print," "Preview," or "Data Output" icon, the processor 122 retrieves the information entered in the report output condition input section UI-52 on the report output condition input screen, creates a report that meets the conditions, and outputs it to the output section 284. Examples of the reports to be output will be explained in the next section.

[0128] Figure 20 shows an output report (Breakdown of Expenditures for Uncompleted Construction Work, Osaka Head Office (2017)). The processor 122 displays such reports on the display unit of the user terminal 20, allowing the user to view the reports (the same applies hereafter to displaying output reports on the display unit). The screen that displays the output reports is referred to as the "output report display screen."

[0129] This section displays the report that processor 122 will show when the "Print" icon on the report output condition input screen mentioned above is pressed. Note that the output, which spans two pages, has been combined into a single figure (explanations for items combined into a single figure will be omitted below).

[0130] As shown in Figure 20, the output report display screen, which displays the output reports, includes a report basic information display unit UI-61 and an accounting information list display unit UI-62.

[0131] The UI-61 form basic information display unit is a display unit that displays the basic information of a form. The basic information on a report includes the title of the report being output. It also typically includes the date and time the report was output.

[0132] In the case of the UI-61 basic information display unit for reports shown in Figure 20, it includes the title, report output period, target department, tax category, report output date and time, and page number.

[0133] The period for report output is the date range specified in the date input field of the report output condition input section UI-52. If no start or end date is specified, the processor 122 displays "First" or "Last," respectively. The tax category is the tax-inclusive or tax-exclusive amount selected in the tax category selection field of the report output condition input section UI-52.

[0134] The report output date and time is the output date and time of the report being output. The term "page" refers to each individual page, especially when multiple copies of a report are being output.

[0135] The department is the one specified in the organizational department input field of the report output condition input section UI-52. If there is no input for a department, the processor 122 causes the output unit 284 to output information for all departments.

[0136] In the example of the report output condition input screen mentioned above, no department is entered, so reports are output for all departments. However, in this example, the diagrams are omitted except for those for the Osaka Head Office and the Tokyo Branch Office (see next figure). In this embodiment, the display unit is based on the second level (for example, Osaka Head Office, Tokyo Branch Office).

[0137] In the accounting information list display unit UI-62, the processor 122 displays a list of accounting information that matches the output conditions (entered in the report output condition input unit UI-52). As shown in Figure 19, the accounting information list display unit UI-62 includes the account title (account title code), project code, project name, and amount (individual and total) as items.

[0138] Figure 21 shows an output report (Breakdown of Expenditures for Uncompleted Construction Work, Tokyo Branch). As mentioned above, since no department is specified, processor 122 outputs reports for all departments.

[0139] Next, we will explain the output of reports related to extended organizations.

[0140] Figure 22 shows an overall view of the extended tissue. The following explanation assumes that the new organization (organization code 0002) shown in Figure 22 has been created as a result of the operations described above.

[0141] Note that (in the UI-22 diagram display unit) the "Company-wide (Department Code 0000)" in the extended organization and the "Company-wide (Department Code 0000)" in the basic organization are different.

[0142] In Figure 22, the Architecture Department hierarchy (department code 0400) and the Civil Engineering Department hierarchy (department code 1500) are new departments. On the other hand, other departments, such as the Head Office Construction Department (department code 0400) and its subordinate organization, the Head Office Construction Section 1 (department code 0410), are existing departments that were part of the basic organizational structure.

[0143] Figure 23 shows a multi-departmental slip information input screen. For explanatory purposes, this section lists multiple departments (Head Office Construction Department, Tokyo Construction Department, Fukuoka Construction Department, and General Affairs Department) involved in the same construction project (Project Name: Department Sample Construction, Project Code: 20250730) together.

[0144] Figure 24 shows the input screen for report output conditions (breakdown of uncompleted construction expenditures, with department code specified). Here, the organization code is set to "0002" for the extended organization in order to output reports related to the extended organization. The department code is entered as "1400," which corresponds to the "Construction Department hierarchy." The construction code is "20250730."

[0145] Figure 25 shows the output report (Breakdown of Expenditures for Uncompleted Construction Work - Building Department Hierarchy). This report outputs information about a specific construction project (project code 20250730) within the Building Department hierarchy (department code 1400).

[0146] In other words, the organizational chart creation system 1 of this embodiment acquires departmental (division) information from construction information and stores it in the storage unit 14. Therefore, it can create an organizational chart that isolates the departments involved in a specific construction project, and can also display (a list) the accounting information related to that specific construction project. In particular, when multiple construction projects are handled by the same extended organization, the ability to consolidate and aggregate the accounts for that extended organization offers a significant advantage in terms of convenience.

[0147] The following section describes the screens for outputting reports other than the breakdown of uncompleted construction expenditures mentioned above.

[0148] Figure 26 shows the screen for inputting report output conditions (list of ordered construction projects). This section explains the input screen used to generate a list of ordered construction projects.

[0149] Note that the rendering of the function icon UI-53 has been omitted (the same applies below). Furthermore, just like in the example above, reports can be generated for extended organizations by entering the organization code of the extended organization on the report output condition input screen (the same applies below).

[0150] As shown in Figure 26, in the report type selection section UI-51, the user can select either "by construction department" or "by sales department". This section explains the case where you select "By Construction Department."

[0151] The report output condition input section UI-52 in the report output condition input screen (list of ordered construction projects) shown in Figure 26 includes an organization / department input field for entering the organization and department (labeled "Construction Department" in Figure 26), a cancellation status selection field (cancelled construction projects), a completion category selection field (completion category), a client code input field (client code), a construction code input field (construction code), a order registration date input field (order registration date), a completed output field (completed output), an ordered output field (ordered output), a contract amount acquisition method selection field (contract amount acquisition method), a date input field (date), an order type selection field (order type), a JV company / overall selection field (Type A JV parent construction output), a tax category selection field (output amount), an approval status selection field (approval status), and a target history selection field (target history).

[0152] This section explains items not described in the report output condition input screen mentioned above (Breakdown of Uncompleted Construction Expenditures, Figure 19). The tax category selection field and approval status selection field are the same as described above, so we will omit further explanation.

[0153] The ordering source code input field is a field where you enter a code (range) associated with the ordering organization.

[0154] The order registration date input field is a field where you enter the date (within a specified range) on which the ordered construction work was registered in the organizational chart creation system 1.

[0155] The "Order Output" field is where you enter the date (range) in which the construction order was received.

[0156] The "Selection Method for Obtaining Contract Amount" field is an input field for selecting which data to obtain when retrieving the contract amount. In this embodiment, there are two options: "Total Contract Amount" and "Calculated from Contract History".

[0157] The order type selection field is an input field for selecting the order type. In this embodiment, the options are "Not Selected," "Single," and "JV." JV is an abbreviation for Joint Venture (a business organization temporarily formed by multiple construction companies to jointly undertake and carry out construction). It is also called a joint venture.

[0158] The JV Company / Overall Selection field allows you to choose whether to output only your company's portion or the entire JV document when it is a joint venture.

[0159] The "Target History Selection" field allows you to choose whether to display "Latest History" or "All History."

[0160] Here's an explanation of the history number. Ordered construction project information is managed using a history number to track changes. The difference between "Latest History" and "All History" lies in whether it outputs information only for the latest history number or information for all history numbers.

[0161] In other words, if you select "Latest History" only, one project will be displayed on one line, while if you select "All History" only, the number of lines corresponding to the history number will be output for each project. Outputting the "Full History" has the advantage of allowing you to check information such as changes to the client, construction manager, contract amount, and contract period in a report.

[0162] Figure 27 shows an output report (list of ordered construction projects).

[0163] The output report display screen, which displays the output report (list of ordered construction projects), includes a UI-61 for displaying basic report information and a UI-63 for displaying the list of ordered construction projects.

[0164] The UI-61 basic information display section of the report includes the title, target department, report output date and time, and page number. Since these items have already been explained, further explanation is omitted.

[0165] As shown in Figure 27, the UI-63 display unit for the list of ordered construction projects includes the following items: classification (completed or incomplete), project code, project name, history number, approval status, information about the client (e.g., owner or client), person in charge (e.g., sales representative or construction manager), contract amount information, whether it is public or private (displayed as "Public / Private Contract"), information about the construction period (e.g., contract period or internal construction period), and memo.

[0166] Figure 28 shows the report output condition input screen (project profit trend table). This section explains the input screen for generating a projected profit trend table.

[0167] As shown in Figure 28, in the projected profit trend table, the user can select either "by construction department" or "by sales department" in the report type selection section UI-51. This section explains the case where you select "By Construction Department."

[0168] The report output condition input section UI-52 in the report output condition input screen (project project profit trend table) shown in Figure 28 includes an organization / department input field for entering the organization and department (labeled "Project Department" in Figure 28), a cancellation status selection field (cancelled project), a completion category selection field (completion category), a project code input field (project code), a processing year / month input field (processing year / month), a project year / month input field (project year / month), a completed output field (completed output), a received output field (received output), an additional project handling selection field (additional project), a common cost allocation amount selection field, a projected contract / projected cost selection field (projected contract / projected cost), a received order type selection field (received order type), a JV company / overall selection field (Type A JV parent project output), and an approval status selection field (processing target (received order approval), processing target (approval)).

[0169] This section explains items not described in the report output condition input screen (Figure 19 or Figure 26) mentioned above.

[0170] The processing year and month input field is used to input the year and month that will serve as the basis for aggregating the contract amount, estimated cost, execution budget, order, and actual cost to be output to the report.

[0171] The forecast month and year input field is for entering the month and year that will serve as the basis for calculating the final forecast cost to be output to the report.

[0172] The "Additional Work Handling Selection" field allows you to choose whether to consolidate the information of the branch work codes into a single main work code for output, or to output it individually for each work code and branch work code.

[0173] In the approval status selection field, this embodiment includes two items: Processing target (order approval) and Processing target (approval). Order approval refers to whether only orders that have been registered / applied for and approved through the workflow should be included (in the output). The processing target (approval) is whether to include only those entries that have been registered / submitted and approved in the workflow for the "execution budget," "order," and "actual cost (voucher)" entered in the process after receiving an order.

[0174] Figure 29 shows the output report (projected profit trend table).

[0175] The output report display screen, which displays the output report (project project profit trend table), includes a basic report information display unit UI-61 and a project project project profit trend list display unit UI-64.

[0176] The report basic information display unit UI-61 includes the display of the title, processing year and month, estimated year and month, target department, report output date and time, and page number.

[0177] The processing month and estimated month are the months entered on the report output condition input screen (project project profit trend table).

[0178] As shown in Figure 29, the UI-64 project profit trend display unit includes the following items: classification (completed or incomplete), project code, project name, contract amount information, cost information (estimated cost information, actual cost information, and final projected cost information), execution budget information, ordering information, and profit information (profit information before final projected cost deduction and (final) projected profit information).

[0179] Note that "Accounting" in the classification column of Figure 29 is synonymous with "Completion," but it refers to completed construction work that is also subject to sales accounting.

[0180] Figure 30 shows the report output condition input screen (project-specific profit and loss management table). This section explains the input screen for generating a profit and loss management report by project.

[0181] As shown in Figure 30, the user can output a project-specific profit and loss management report by selecting "Project-Specific Profit and Loss Management Report" in the report type selection section UI-51.

[0182] The report output condition input section UI-52 in the report output condition input screen (project-specific profit and loss management table) shown in Figure 30 includes an organization / department input field for entering the organization and department (labeled "Project Department" in Figure 30), a cancellation / cancellation selection field (cancelled project), a completion classification selection field (completion classification), a completion accounting classification selection field (completion accounting classification), a project code input field (project code), accounting period, year and month, output type (output), financial statements to include in the current period, and an approval status selection field (processing target (order approval), processing target (approval)).

[0183] This section explains items not described in the report output condition input screens mentioned above (Figures 19, 26, or 28).

[0184] The "Accounting Period" field is where you enter the accounting period that will serve as the basis for aggregating costs and sales up to the previous period, which will be output to the report.

[0185] The year and month field is where you enter the date that serves as the basis for aggregating the contract amount, estimated cost, current period costs, and current period sales to be output to the report.

[0186] Figure 31 shows an output report (profit and loss management table by project).

[0187] The output report display screen, which displays the output report (project-specific profit and loss management table), includes a basic report information display unit UI-61 and a project-specific profit and loss information display unit UI-65.

[0188] The report basic information display unit UI-61 includes the display of the title, accounting period, target department, report output date and time, and page number. The accounting period is the one entered on the report output conditions input screen (project-specific profit and loss management table).

[0189] As shown in Figure 31, the UI-65 project-specific profit and loss information display unit includes the following items: classification (completed or incomplete), completion accounting classification, presence or absence of canceled projects, project code, project name, construction period information (internal construction period, etc.), contract amount information, estimated cost information, estimated gross profit information, cost information (costs up to the previous period, costs incurred in the current period, and cumulative costs, etc.), progress, sales information (sales up to the previous period, sales incurred in the current period, and cumulative sales, etc.), profit information (profits up to the previous period, profits incurred in the current period, and cumulative profits, etc.), and provision information (balance of the aforementioned loss provision, estimated amount of loss provision for the current period, and balance of the current period loss provision, etc.).

[0190] Figure 32 shows the construction inquiry screen. The construction inquiry screen is a screen that allows users to inquire about construction information. Processor 122 displays construction information on the construction inquiry screen according to the user's search criteria.

[0191] In this embodiment, the processor 122 can display construction information in a list. Figures 32(a) to 32(c) show a single horizontal screen divided into upper, middle, and lower sections, respectively.

[0192] As shown in Figure 32, the construction inquiry screen includes a construction inquiry condition input section UI-71, a construction search button UI-72, and a construction list display section UI-73.

[0193] When a user enters search criteria into the project inquiry criteria input section UI-71 and presses the project search button UI-72, the processor 122 displays a list of existing projects that match the search criteria in the project list display section UI-73.

[0194] As shown in Figure 32, the UI-71 construction inquiry condition input unit includes a processing year and month input field (labeled "Processing Year and Month" in Figure 32), an output pattern selection field (Output Pattern), a construction code input field (Construction), a client input field (Client), a person in charge designation field (Person in Charge Designation), a department code input field (Department in Charge), and a person in charge input field (Person in Charge).

[0195] The processing year and month input field is where you enter the year and month that will serve as the basis for aggregating numerical information such as the contract amount, execution budget amount, sales amount, and payment amount entered for each process.

[0196] The output pattern selection field allows you to pre-set multiple patterns of items and their order for output, which you can then select and view.

[0197] The construction code input field is where you enter the construction code, and you can also specify branch codes, etc.

[0198] The ordering source input field is an input section for entering the ordering source, and in this embodiment, the user can select the ordering source from a list displayed in a pull-down menu.

[0199] The "Assignment" field is a selection field for choosing whether the person in charge is in charge of construction or sales.

[0200] The Department Code Input Field is where you enter the department code of the department you are responsible for. In this embodiment, the organization code and department code can be entered. That is, by entering the organization code of the extended organization, a list of construction projects related to the extended organization can be output.

[0201] The person in charge input field is an input section for entering the person in charge. In this embodiment, the user can select a person in charge from a list displayed in a dropdown menu.

[0202] As shown in Figure 32, the user has selected December 2025 as the processing month and "Construction Information" as the output pattern, and has selected the organization code "0000" and department code "0400" (Head Office Construction Department). The department in charge is the Construction Department.

[0203] The processor 122 displays the relevant construction project on the construction project list display unit UI-73. Since no project code was specified as a search criterion, all relevant projects are displayed in the output.

[0204] In this case, the processor 122 displays the details of the construction work in the construction list display unit UI-73. The details of the construction project include the project code, sub-project code, official project name, order date, approval status, completion category, completion accounting category, project department, project manager, sales department, sales manager, project type name, contract period, internal project period, order category, order type, order method, public / private category, official name of client, contract amount information, sales amount, execution budget amount, payment amount (cumulative), budget balance (budget - cost), profit amount (contract amount - cost), invoice amount (cumulative), and received amount (cumulative).

[0205] [Table 1]

[0206] Table 1 summarizes the above information (1 example per row, 10 examples) into a sheet (after exporting it as a CSV file). Tables 1(a) and 1(b) are a single table divided into upper and lower sections.

[0207] With the above configuration, the processor 122 provides a GUI (Graphical User Interface) to the user terminal 20, allowing the user to intuitively create an organizational chart in the organizational chart creation system 1. In particular, since subordinate departments can be created by adding a node on a node already placed on the organizational chart display unit UI-22, adding and editing organizations is easy. Furthermore, since the organizational chart display unit UI-22 shows the entire organizational chart, it has the advantage of making it easier to prevent mistakes such as adding a new node to the wrong node. The same applies to node deletion; unwanted nodes can be deleted by directly pointing to them, allowing for intuitive operation. Furthermore, since the parent, subordinate, and adjacent departments of a node are displayed in the organizational chart display unit UI-22, it has the advantage of making it easier to prevent mistakes such as accidentally deleting a node that should not be deleted. Furthermore, in industries such as construction, where multiple departments collaborate on multiple tasks for each project, there is an advantage in being able to create an organizational chart for an expanded organization consisting of multiple departments, and to create and output various (accounting) reports related to that expanded organization (such as a breakdown of uncompleted construction expenditures, a list of contracted construction projects, a projected profit trend table, and a project-specific profit and loss management table). Furthermore, all construction projects can be inquired about, and since these projects are linked by the relevant departments, clients, and construction periods, users can obtain various types of information at the level they want, such as by department or by project.

[0208] 2. Program Processing <Organizational chart creation process> The program processing performed in the organizational chart creation system 1 of this embodiment will now be described.

[0209] In this embodiment, the processor 122 performs organizational chart creation processing based on the organizational chart creation program P1. The organization chart creation program P1 includes at least a department information acquisition program P12, an organization chart drawing program P14, and a form creation program P16. Based on these programs, the processor 122 executes department information acquisition processing, organization chart drawing processing, and form creation processing, respectively. That is, each program causes the computer to function as department information acquisition means, organization chart drawing means, and form creation means by the execution of department information acquisition processing, organization chart drawing processing, and form creation processing by the processor 122. Also, at least each of the department information acquisition program P12, the organization chart drawing program P14, and the form creation program P16 provides a department information acquisition method, an organization chart drawing method, and a form creation method, respectively, by cooperating with hardware.

[0210] Note that these programs are an example for explaining the invention. Each program is not mutually exclusive, and for example, the information acquired in the department information acquisition processing may be acquired during the form creation processing.

[0211] In the following description, if a flowchart is included, each process in the flowchart may be in any order as long as there is no contradiction in the process content. Also, each process in the flowchart may omit a part of each process constituting the flowchart or add a new process as long as there is no contradiction in the process content. Also, the processor that executes each process in the flowchart may be changed to another processor as long as there is no contradiction in the process content. In that case, if necessary, a part of each process constituting the flowchart may be omitted or a new process may be added as long as there is no contradiction in the process content. In the figure showing the flowchart, the steps are abbreviated as "S".

[0212] <2-1. Department Information Acquisition Processing> In the department information acquisition processing, the processor 122 acquires information regarding the departments constituting the organization.

[0213] The department information acquisition process is as follows: Organization information acquisition process that acquires organizational information including the organization's organization code or organization name as organizational identification information. A department information acquisition process that acquires department information including the department code or department name of the departments constituting the aforementioned organization as department identification information. A project information acquisition process that acquires project information including the project code or project name of the project in which the aforementioned department is involved as project identification information, and This includes a project accounting information acquisition process that acquires the accounting information of the aforementioned project.

[0214] As will be explained in detail in section 3. Data, in this embodiment, the department identification information includes the department code and department name, and further includes the department's accounting information and / or the department's contracted construction information (project information).

[0215] <2-2. Organizational Chart Drawing Process> In the organizational chart drawing process, processor 122 draws the organizational chart on the workspace.

[0216] The organizational chart drawing process is as follows: A first node rendering process that places the first node corresponding to the department on the workspace. (Either by including it from the start when creating the workspace, or by having the user include it.) Node operation processing that operates the node corresponding to the department on the workspace, Node organizational chart storage process, which stores the organizational chart represented by the aforementioned nodes (and the relationships between nodes) in a storage unit. This includes an organizational chart identification process that associates the organizational chart with organizational identification information.

[0217] Here, the organizational chart drawing process is performed. This includes an organizational chart reading and display process that accepts organizational identification information (from the user) and displays the corresponding organizational chart in the workspace.

[0218] The node operation process that operates the aforementioned node is: In a workspace displayed on the computer's display unit, a node addition process is performed by a user who adds a node by specifying a node that corresponds to the department and is already installed. Node relationship rendering process that represents the relationship between the already placed node and the new node on the workspace (by indentation or edges), Node relationship storage processing, which stores the relationship (tree structure) between the already deployed node and the new node in the storage unit. In a workspace, a node deletion process is performed by a user who deletes a node that corresponds to the department and is already installed, by specifying the node that corresponds to the department. In the workspace, a node sorting process is performed by the user specifying a node that corresponds to the department and is already deployed, thereby sorting (rearranging the display order) the nodes contained in that node in order of department identification information (department code), and, The process includes a node movement operation in which a node is moved within a workspace by a user's node movement operation, which specifies a node that corresponds to the department and is already installed in the workspace.

[0219] Furthermore, the node addition process is as follows: This includes a process for adding subordinate department nodes, which adds a subordinate department to a node by a user's node addition operation in the workspace, where the user specifies a node that corresponds to a department and is already installed.

[0220] Furthermore, the node addition process is as follows: Input department code acquisition process (based on user input) to obtain the department code of a newly added node. A duplicate organization code determination process that determines whether the department code of the newly added node is the same as an existing one. (1) When the department code of the newly added node is an existing department code, an existing department addition process for adding the department corresponding to the department code, and (2) When the department code of the newly added node is not an existing department code, a new department name acquisition process for acquiring the department name of the newly added node, are included.

[0221] FIG. 33 is a flowchart showing the organization chart drawing process. The processor 122 starts the organization chart drawing process by a predetermined operation (such as new creation or organization chart reference) of the user related to the organization chart creation on the extended organization chart creation screen.

[0222] The processor 122 determines whether to create a completely new organization chart (step 11). That is, if there is an operation of the user related to the new creation of the first node (FIG. 6) (step 11 Yes), the processor 122 causes a new node to be drawn on the workspace (organization chart display unit UI-22) (step 12).

[0223] On the other hand, if there is an operation of the user related to the reference of an (existing) organization (FIG. 15, etc.) (step 11 No), the processor 122 displays an organization search screen on the workspace. Then the processor 122 acquires the organization code input by the user (step 13), and displays the organization chart of the organization corresponding to the organization code on the workspace (organization chart display unit UI-22) (step 14).

[0224] Receiving the user's node addition operation on the workspace (organization chart display unit UI-22) (step 15), the processor 122 causes the node corresponding to the department to be drawn on the organization chart display unit UI-22.

[0225] Also, the processor 122 acquires the department code input in the department information input unit UI-23 (step 16). Here, the processor 122 determines whether the input department code is an existing one (step 17).

[0226] If the department code entered in the department information input unit UI-23 is an existing one (step 17 Yes), the processor 122 adds the node corresponding to the department with that department code to the workspace (organizational chart display unit UI-22).

[0227] In this embodiment, the processor 122 adds the department relating to the new node as a subordinate department of the department relating to the node that is the target of the addition operation (the original node).

[0228] In this embodiment, the processor 122 displays the new node one level below the original node (like an indentation) so that the user can easily see that the new node is a subordinate department (see Figure 9).

[0229] Furthermore, processor 122 uses indentation to represent the node being added and the new node. The new node is placed below the node being added, and the new node is indented. In other words, the relationship between the already placed nodes and the new nodes is represented on the workspace by indentation (node ​​relationship rendering process).

[0230] Furthermore, the method of representing the relationship between the original node and the newly added node on the workspace is not limited to representing the relationship between nodes with indentation. For example, possible methods include displaying departments within the same group in the same box (in this case, the box can also be considered a node), displaying them in the same color, or connecting nodes with edges.

[0231] Returning to Figure 33, if the department code entered in the department information input unit UI-23 is not an existing one (step 17 No), the processor 122 adds a node for the (new) department to the organizational chart display unit UI-22 (step 19).

[0232] Then, the processor 122 retrieves the names of departments (official names and abbreviations, etc.) entered into the department information input unit UI-23 (step 20), and reflects the names of the departments in the nodes of the organizational chart display unit UI-22 (step 21).

[0233] In this embodiment, if the department code entered in the department information input unit UI-23 is an existing one, the processor 122 prohibits the input of the department name, etc., in the department information input unit UI-23. On the other hand, if the entered department code is not an existing one, the processor 122 allows the input of the department name, etc., in the department information input unit UI-23.

[0234] If you then add more nodes (step 22No), the processor 122 repeats the process described above from step 15 onwards. If the process ends without adding any nodes (Step 22 Yes), the processor 122 terminates the organizational chart drawing process.

[0235] <2-3. Report Creation Process> In the report creation process, processor 122 outputs accounting reports corresponding to the departments in the organizational chart. For information on the types of reports to be output or the UI, please refer to section 1.UI.

[0236] The report creation process is, A process to obtain the user's selection regarding the type of report to be output. A report output condition acquisition process that acquires the output conditions for the selected report, This includes a report output process that outputs a report that conforms to the aforementioned output conditions.

[0237] The aforementioned process for obtaining report output conditions is as follows: Organization condition acquisition process to obtain organizational identification information (organization code or organization name) (as a condition) (As a condition) A department condition acquisition process that acquires department identification information (department code or department name). (As a condition) Project condition acquisition process to acquire project identification information (project code (construction code) or project name (construction name)), This includes a process to retrieve the title of the document.

[0238] Furthermore, depending on the report to be output, the report output condition acquisition process is performed as follows: Time condition acquisition process to obtain the time conditions for the report to be output. (As a condition) A process to obtain a unique client code or client name for the client. Order type condition acquisition process to acquire the order type (as a condition) (single-party or joint venture), This includes an approval condition retrieval process that obtains whether or not approval has been granted (as a condition).

[0239] Here, the time condition is, for example, (1) The completion date of the completed construction work mentioned above in the breakdown of expenditures for uncompleted construction work, the list of contracted construction work, or the projected profit trend table (output for completed work), (2) The date of the basis for the aggregated data mentioned above in the breakdown of expenditures for uncompleted construction work or the list of contracted construction work, (3) Accounting period in the profit and loss management statement by project, or (4) Processing date in the list of construction projects, And so on.

[0240] To elaborate, the date refers to the range of voucher dates for the vouchers included in the calculation, such as in the breakdown of work-in-progress expenditures. It is the range within which information from vouchers indicating the incurrence of construction costs (vouchers entered under the work-in-progress expenditures account) is aggregated. Furthermore, if it's a list of contracted construction projects, it will be the date range for which the contract amount is calculated.

[0241] The same applies to income statements and balance sheets; processor 122 obtains the conditions for outputting reports for one year, three years, etc.

[0242] The aforementioned report output process is as follows: • Departmental accounting information output process that outputs accounting information for a department based on department identification information. • Project-specific accounting information output process that outputs accounting information for a given project based on project identification information, or This includes a department / project-specific accounting information output process that outputs accounting information for a given project within a given department, based on department identification information and project identification information (especially for each of several different departments).

[0243] Here, the departmental accounting information output process, the project-based accounting information output process, and the departmental / project-based accounting information output process are all, The process for obtaining account information (information contained in the account master among accounting information), and This includes subject-level aggregation processing, which aggregates data for each subject.

[0244] For information about the subject master data, please refer to section 3, "Data." The processor 122 retrieves data from the account master that is necessary for creating vouchers, income statements, balance sheets, or the various reports mentioned above, such as account names or debit / credit classifications.

[0245] Then, processor 122 performs subject-level aggregation (subject-level aggregation processing) based on the information obtained in the subject information acquisition process.

[0246] For example, this could include a summary of cash disbursements (usually within a certain period) for a particular department and / or project (construction). For this aggregation, publicly known techniques used in accounting software and other applications can be appropriately employed.

[0247] The process of creating a report is, for example, A work-in-progress expenditure breakdown output process that outputs a work-in-progress expenditure breakdown including at least the department information, the project information, the account titles (of the work-in-progress expenditure breakdown), and the amounts (for at least a portion of the account titles), A process for outputting a list of ordered construction projects, which outputs a list of ordered construction projects that includes at least the department information, the project information, information about the client (for each ordered construction project), information about the contract amount (for each ordered construction project), and information about the construction period (for each ordered construction project). A project project profit trend output process that outputs a project project profit trend table including at least the department information, the project information, contract amount information (necessary for outputting the project project profit trend table), cost information (necessary for outputting the project project profit trend table), and profit information (necessary for outputting the project project profit trend table). The process may include outputting a project-specific profit and loss management table that outputs a project-specific profit and loss management table that includes at least the department information, project information, construction period information (necessary for outputting a project-specific profit and loss management table), cost information (necessary for outputting a project-specific profit and loss management table), sales information (necessary for outputting a project-specific profit and loss management table), and profit information (necessary for outputting a project-specific profit and loss management table).

[0248] These processes are responsible for outputting the breakdown of uncompleted construction expenditures, the list of contracted construction projects, the projected profit trend table, and the project-specific profit and loss management table, respectively, as explained in section 1. User Interface.

[0249] These processes (outputting a breakdown of uncompleted construction expenditures, outputting a list of ordered construction projects, outputting a project profit trend table, and outputting a project-specific profit and loss management table) are not processes that processor 122 executes separately (exclusively) from the various processes included in the report creation process described above (such as report output processes), but rather they overlap with the above processes.

[0250] For example, the output process for the breakdown of expenditures for uncompleted construction work, the output process for the list of contracted construction work, the output process for the projected profit trend table, and the output process for the profit and loss management table by construction work can each be considered a form of report output processing.

[0251] With the above configuration, processor 122 creates an organizational chart on the workspace in response to user operations. The organizational chart includes nodes corresponding to the departments of the organization, and the relationships between the nodes indicate the relationships between departments. The processor 122 adds a new node to the workspace based on a user's node addition operation, which specifies an already deployed node. In particular, in this embodiment, the processor 122 adds the department related to the new node as a subordinate department of the department related to the original node. Furthermore, in this embodiment, the operation performed by specifying the node is an operation of selecting the node by pressing it on the workspace, allowing the user to add nodes and perform other operations intuitively. In other words, the user can create an organizational chart with intuitive operations. Users can input the organizational identification information of the organization they created (extended organization) and other necessary information (project identification information, duration information, etc.) to output various reports.

[0252] 3. Data The data handled by the organizational chart creation system 1 of this embodiment will be explained below with reference to diagrams. The organizational chart creation system 1 of this embodiment includes an organizational chart creation database D1 in the storage unit 14 (data storage unit 14b) of the server 10. The organizational chart creation database D1 includes a user information table D11, a user permission details table D12, an organization master D21, a department master D22, a departmental account permission master D23, a project (construction) master D31, and a voucher table D42.

[0253] User information table D11 is a database containing data (user data) about users who use the organizational chart creation system 1.

[0254] User information table D11 includes, as (data) items, a unique user ID for each user, as well as username, security (authentication) related information, employee code, employee name, company code, authority level information, processing department application start date, and processing department code.

[0255] In this embodiment, the user is an employee, and the employee belongs to the company. The employee code is a unique code for each employee.

[0256] Here, security-related information includes not only passwords (passphrases), but also, for example, hash values ​​of passwords, key (public key or private key) information, biometric authentication information, etc., and may include publicly known information.

[0257] The company code is a unique code for each company. The organizational chart creation database D1 has a separate company table where company codes are associated with company names, etc.

[0258] In addition to the above, the user information table D11 or the company table may contain address, contact information, or payment information.

[0259] The permission level information is information (permission level code) related to the permission level that is set in advance on the permission registration screen (not shown). By setting the availability of each function in the organizational chart creation system 1 on a per-permission level code basis, users can utilize each function according to their assigned permission level.

[0260] User Permission Details Table D12 is a database that contains data related to user permissions (user permission data).

[0261] The user permission details table D12 includes the following (data) items: User ID, Company Code, Operation Permissions, Processing Department Application Start Date, and Processing Department Code.

[0262] When the processor 122 registers the departments in which user information can be processed, it stores in the storage unit 14 the department in which the information was saved, as the processing department application start date.

[0263] Organization Master D21 is a database that contains data about organizations (organizational data).

[0264] Organization Master D21 includes, as (data) items, a unique organization code for each organization, as well as a company code, organization name, organization name in kana, and effective start date (see Figure 15).

[0265] Department Master D22 is a database that contains data related to departments (department data).

[0266] Department Master D22 includes the following data items: a unique department code, company code, organization code, effective start date, department abbreviation, department kana abbreviation, department full name, hierarchy number, hierarchy name, node path, aggregation unit (start), and aggregation unit (end).

[0267] A node path is hierarchical information within a departmental tree. It represents, in path format, the position of a department under which other departments it belongs.

[0268] The aggregation unit is a numerical representation of which departments are included in the aggregation range, as various types of information, such as accounting information, are aggregated hierarchically within the departmental tree.

[0269] The Departmental Subject Authority Master D23 is a database containing data on subjects that can be edited by each department (Departmental Subject Authority Data).

[0270] The Departmental Account Authority Master D23 includes the following (data) items: Organization Code, Department Code, Department Application Start Date, and Account Authority Classification.

[0271] Subject permission categories are classifications of usage rights for subjects (set for each department). On the subject permission registration screen (not shown), you can pre-set whether a subject is usable or unusable for each subject permission category code, allowing you to set whether each subject is usable or unusable for each department according to its permission category.

[0272] Project (Construction) Master D31 is a database that contains data (project (construction) data) related to (ordered) projects (construction).

[0273] Project (construction) master D31 includes the following data items: a unique construction code, construction branch code, cancellation category, completion category, completion accounting category, common cost category, order date, contract start date, contract end date, internal construction start date, internal construction end date, handover date, completion confirmation date, construction abbreviation, construction kana abbreviation, construction official name, consumption tax category, taxable category, contract amount (information), tax-exclusive amount, tax-inclusive amount, consumption tax amount, construction cost, construction department code, construction manager code, sales department code, sales manager code, construction type code, site representative code, chief engineer code, supervising engineer code, designer code, client code, payment destination code, ordering source code, ordering source contact person, payment date, order type, order category, order method, JV category, and memo.

[0274] Subject Master D41 is a database that contains data related to subjects (subject data).

[0275] The account master D41 includes the account code, breakdown code, cancellation category, account name (in kana), account abbreviation, and official account name), account category, debit / credit category, record category, calculation category, consumption tax category, taxable category, taxable category, construction requirement category, expense item requirement category, safety association requirement category, other deduction requirement category 1, aggregation destination account code, aggregation destination breakdown code.

[0276] The voucher table D42 is a database that contains data related to vouchers (and by extension, accounting) (voucher data or accounting data).

[0277] The voucher table D42 includes the following (data) items: voucher type, voucher number, line number, receipt date, account code, breakdown code, department code, customer code, project code, project sub-code, work type code, expense code, sub-code, sub-name, standard name, purchase order number, payment date, consumption tax type, taxable type, accounting type, invoice amount, assessed amount, tax-exclusive amount, tax-inclusive amount, consumption tax amount, voucher amount, quantity, unit, unit price, description, and accounting period.

[0278] With the configuration described above, the organizational chart creation system 1 contains information related to projects (construction work), information related to departments, and accounting information related to those projects (construction work) and departments, and can output various reports and other information desired by the user.

[0279] 4. Hardware Configuration Figure 34 is a diagram (network diagram) showing an overview of the organizational chart creation system 1 of this embodiment. As shown in Figure 34, the organizational chart creation system 1 comprises a server 10 and user terminals 20. These devices are connected via a network N, which is, for example, the internet. The following describes each piece of hardware.

[0280] <Server 10> Server 10 is a computer used to run the organizational chart creation program P1. In other words, the server 10 has software installed (application software including the organizational chart creation program P1) for operating the organizational chart creation system 1 according to this embodiment, and the processor 122 executes various processes according to the functions of the software.

[0281] Although only one server 10 is shown in Figure 34, the number is not limited to one and may be implemented using multiple servers. For example, multiple servers may be used from the standpoint of load balancing, functional isolation, availability, or security. Server 10 may, for example, utilize a computer provided by a cloud service provider, or it may be a computer provided by the user and managed within an internal network.

[0282] Figure 35 is a hardware configuration diagram of server 10. As shown in Figure 35, the server 10 comprises a control unit 12, a storage unit 14, and a communication control unit 16. The control unit 12 also comprises a processor 122, a ROM 124, a RAM 126, and a timing unit 128. The basic functions of each will be explained in detail later.

[0283] The control unit 12, which includes a processor 122, also functions as an organizational chart creation unit in the server 10 (not shown). The organizational chart creation unit executes the organizational chart creation program P1 to perform the organizational chart creation process. In this embodiment, the processor 122 is a CPU (Central Processing Unit).

[0284] Furthermore, one program may include other programs. For example, in this embodiment, the organizational chart creation program P1 includes a department information acquisition program P12 and an organizational chart drawing program P14, etc.

[0285] As shown in Figure 35, the storage unit 14 includes a program storage unit 14a and a data storage unit 14b, and stores programs and data necessary for various processes.

[0286] For example, the program storage unit 14a stores not only the organizational chart creation program P1 according to this embodiment, but also control programs for controlling equipment connected to the server 10, such as a communication control program for controlling the communication control unit 16.

[0287] As shown in Figure 35, the communication control unit 16 is a device that communicates between the server 10 and an external terminal, such as the user terminal 20 described later. As shown in Figure 34, the communication control unit 16 connects the server 10 to the network N.

[0288] In addition to the above, the server 10 may also include an input unit (e.g., a keyboard) for inputting commands and data, and an output unit (e.g., an audio output device) for outputting information in some form (not shown). Furthermore, it may include additional devices necessary for the use of this embodiment, or devices to improve convenience for the use of this embodiment.

[0289] <User terminal 20> The user terminal 20 is an information processing device for users to use the organizational chart creation system 1. Users access the organizational chart creation system 1 by accessing the server 10 using the user terminal 20.

[0290] Figure 36 is a hardware configuration diagram of the user terminal 20. As shown in Figure 36, the user terminal 20 includes a control unit 22, a storage unit 24, a communication control unit 26, and an input / output unit 28 (input unit 282 and output unit 284).

[0291] The control unit 22 includes a processor 222, ROM, RAM, and a timing unit. The output unit 284 includes a display unit 284a. Explanations that overlap with previously explained content or relate to basic functions described later will be omitted.

[0292] In this embodiment, the user terminal 20 is a desktop PC. However, the user terminal 20 is not limited to this and may be a portable device such as a smartphone or tablet.

[0293] There is no need to install a specific application on the user terminal 20; the organizational chart creation system 1 can be used by accessing the server 10, etc., via the internet.

[0294] Various processes include output (screen display, audio output) based on information obtained from server 10, receiving user input, and various communications. For example, when a user launches the user application P20, the processor 222 of the user terminal 20 communicates with the server 10 via the network N and executes various processes.

[0295] In this embodiment, the user application P20 is installed on the user terminal 20 via the network N or via a storage medium containing the user application P20.

[0296] (Explanation of the basic functions of a computer) The following describes the control unit (processor, ROM, RAM, timing unit), storage unit, communication control unit, input unit, and output unit. In any of the terminals in this embodiment, the connection configuration (network topology) between functional units is not particularly limited. For example, it may be a bus type, a star type, a mesh type, or the like.

[0297] The processor performs information processing and controls various devices according to programs stored in ROM or other memory units. In this embodiment, the processor is a CPU (Central Processing Unit).

[0298] However, the processor is not limited to a CPU. A CPU, DSP (Digital Signal Unit), GPU (Graphics Processing Unit), GPGPU (General Purpose computing on GPU), TPU (Tensor Processing Unit), or ASIC (Application Specific Integrated Circuit) may be used individually or in combination. For example, a processor that integrates a CPU and a GPU is called an APU (Accelerated Processing Unit), and such a processor can also be used.

[0299] ROM is read-only memory that contains various programs and data pre-stored for the processor to perform various control and calculations.

[0300] RAM is random-access memory used by the processor as working memory. Various areas can be reserved within this RAM for performing the various processes described in this embodiment.

[0301] The timing unit performs timing processing, including the acquisition of time information. If the computer is equipped with a communication control unit, it may acquire time information from an external source using NTP (Network Time Protocol).

[0302] A memory unit is a device for storing information such as programs and data. It is also called a storage unit. The memory unit can be either internal or external. The storage unit may also utilize online storage connected via a network. For example, technologies such as SAN (Storage Area Network) or NAS (Network Assisted Storage) may be used.

[0303] The storage unit includes a storage medium capable of reading and writing data, and a drive for reading and writing to the storage medium. Storage media include internal and external types, such as HD (hard disk), CD-ROM, and flash memory. Examples of drives include HDDs (hard disk drives) and SSDs (solid state drives).

[0304] The memory unit comprises a program storage unit and a data storage unit as functional units. The program storage unit stores control programs for controlling various devices, such as communication control programs for controlling communications.

[0305] A communication control unit is a device for facilitating communication between terminals and other devices. The communication control unit connects the terminals equipped with the communication control unit to the network.

[0306] Here, the network is not limited to external networks such as the internet, but may also refer to internal networks such as LANs (Local Area Networks). Note that internal networks may be omitted in network diagrams. For example, a server may be located on the same internal network as a terminal.

[0307] The communication method of the communication control unit is a known method, and either a wired or wireless method is applied depending on the equipment. For example, if the device is a desktop PC, both wired and wireless connections are possible, while if the device is a smartphone, a wireless communication method is possible.

[0308] For wired connections, communication methods defined in standards such as IEEE 802.3 (e.g., bus-type or star-type wired LANs) can be suitably used, but other communication methods such as those defined in IEEE 802.5 (e.g., ring-type wired LANs) may also be used.

[0309] For wireless communication, a communication method defined by, for example, IEEE 802.11 (e.g., Wi-Fi) can be suitably used. However, other methods such as IEEE 802.15 (e.g., Bluetooth®, BLE (Bluetooth® Low Energy)), IEEE 802.16 (e.g., WiMAX), ZigBee®, 920MHz band wireless (e.g., Wi-SUN), or optical communication methods such as infrared communication may also be used.

[0310] The input and output sections are devices responsible for input and output to and from the terminal, respectively. The input and output sections are sometimes collectively referred to as the input / output section. The input unit is a device that receives input from the user. Examples of such input units include keyboards, pointing devices such as mice, trackpads, tablets, or touch panels.

[0311] If the device is a tablet or smartphone and the input unit is a touch panel, the input unit is located on the surface of the display unit that displays images, such as a touchscreen. In this case, the input unit identifies the user's touch position corresponding to the various operation icons displayed on the display unit and accepts input from the user.

[0312] The output unit is a device for outputting, for example, images, audio, or documents. Output devices include, for example, display devices such as touchscreens and displays (liquid crystal displays and organic EL displays), audio output devices such as speakers, and document output devices such as printers.

[0313] (modified version) The present invention is not limited to the embodiments described above, but includes various modifications to the embodiments described above, without departing from the spirit of the invention.

[0314] Aspects of the present invention, including this embodiment, have the following characteristics. The following corresponds to the claims at the time of filing the application. However, due to amendments to the claims after filing, the description of the claims may differ. (1) In a first embodiment, the present invention provides an organizational chart creation program characterized in that the computer functions as: an organizational information acquisition means for acquiring organizational information including the organizational code or organizational name of an organization as organizational identification information; a departmental information acquisition means for acquiring departmental information including the departmental code or departmental name of a department constituting the organization as departmental identification information; a project information acquisition means for acquiring project information including the project code or project name of a project in which the department is involved as project identification information; a project accounting information acquisition means for acquiring accounting information for the project; a node addition means for adding a new node by a user node addition operation performed by specifying a node that corresponds to the department and is already placed in a workspace displayed on the computer's display unit; a node relationship drawing means for representing the relationship between the already placed node and the new node on the workspace; a node organizational chart storage means for storing the organizational chart represented by the nodes in a storage unit; an organizational chart identification means for associating the organizational chart with organizational identification information; an organizational chart reading and display means for receiving input of organizational identification information and displaying the corresponding organizational chart in the workspace; and a department / project-specific accounting information output means for outputting accounting information for the project of the department from the departmental identification information and the project identification information. (2) In a second embodiment, the organizational chart creation program according to the first embodiment is provided, characterized in that the node addition means includes an input department code acquisition means for acquiring the department code of a newly added node; a duplicate organizational code determination means for determining whether the department code of the newly added node is an existing one; (1) an existing department addition means for adding a department corresponding to the department code if the department code of the newly added node is an existing department code; and (2) a new department name acquisition means for acquiring the department name of the newly added node if the department code of the newly added node is not an existing department code. In this case, it prevents the same department code from being assigned to different departments, and also improves user convenience by appropriately performing two different processes—reading existing departments and adding new organizations—depending on whether the department code is existing or new. (3) In a third aspect, the organizational chart creation program according to the first aspect is provided, characterized in that the node addition means is a subordinate department node addition means that adds a subordinate department to a node by a user's node addition operation in the workspace, which specifies a node that corresponds to the department and is already installed. In this case, there is an advantage in that operations become easier, especially when the organization has a hierarchical structure with three or more levels. (4) In a fourth aspect, the organizational chart creation program described in the first aspect is provided, further characterized in that the computer functions as a node deletion means for deleting a node by a user who performs a node deletion operation in the workspace by specifying a node that corresponds to the department and is already installed, and as a node sorting means for sorting the nodes included in a node by department code order by a user who performs a node sort operation in the workspace by specifying a node that corresponds to the department and is already installed. In this case, sorting the organizational chart by node sorting has the advantage of improving its readability for the user. (5) In a fifth embodiment, the organizational chart creation program according to the first embodiment is provided, further characterized in that the computer functions as an output means for outputting a breakdown of work-in-progress expenditures, which includes at least the department information, the project information, the account titles, and the amounts of the account titles. In this case, there is the advantage of being able to output a breakdown of work-in-progress expenditures that includes departmental information and project information (especially for each project). (6) In a sixth embodiment, the organizational chart creation program described in the first embodiment is provided, further characterized in that the computer functions as an output means for outputting a list of ordered construction projects, which includes at least the department information, the project information, information about the client, information about the contract amount, and information about the construction period. In this case, there is the advantage of being able to output a list of contracted construction work that includes departmental information and project information (especially for each project). (7) In a seventh aspect, the organizational chart creation program described in the first aspect is provided, further characterized in that the computer functions as a construction project project profit trend output means that outputs a construction project project profit trend table including at least the department information, the project information, the contract amount information, the cost information, and the profit information. In this case, there is the advantage of being able to output a projected profit trend table that includes departmental information and project information (especially for each project). (8) In the eighth aspect, the organizational chart creation program described in the first aspect is provided, further characterized in that the computer functions as a means for outputting a profit and loss management table by construction project, which outputs a profit and loss management table by construction project that includes at least the department information, the project information, the construction period information, the cost information, the sales information, and the profit information. In this case, there is the advantage of being able to output a project-specific profit and loss management report that includes departmental information and project information (especially for each project). (9) In the ninth aspect, an organization information acquisition unit acquires organization information that includes the organization's organization code or organization name as organization identification information. A department information acquisition unit that acquires department information including the department code or department name of the departments constituting the aforementioned organization as department identification information. A project information acquisition unit that acquires project information including the project code or project name of the project in which the aforementioned department is involved as project identification information. Project accounting information acquisition unit that acquires accounting information for the aforementioned project, In the workspace displayed on the computer's display unit, a node addition unit adds a new node by specifying a node that corresponds to the department and is already installed, as performed by the user in a node addition operation. A node relationship drawing unit that represents the relationship between the already placed nodes and the new nodes on the workspace. A node organizational diagram storage unit that stores the organizational diagram represented by the aforementioned nodes in a storage unit. Organizational chart identification unit that associates the organizational chart with organizational identification information, An organizational chart reading and display unit that accepts input of organizational identification information and displays the corresponding organizational chart in the workspace, and A department / project-specific accounting information output unit outputs accounting information for a given project within a given department, based on the department identification information and project identification information of that department. The present invention provides an organizational chart creation system characterized by comprising the following features. The advantages in this case are the same as those in the first embodiment, so we will omit the explanation (see the effects of the invention described above). (10) In the tenth aspect, the processor performs an organization information acquisition step in which it acquires organization information including the organization code or organization name of the organization as organization identification information; a department information acquisition step in which the processor acquires department information including the department code or department name of the departments constituting the organization as department identification information; a project information acquisition step in which the processor acquires project information including the project code or project name of the project in which the department is involved as project identification information; a project accounting information acquisition step in which the processor acquires accounting information for the project; and a user node addition operation performed by the processor by specifying a node that corresponds to the department and is already installed in the workspace displayed on the computer's display unit. The present invention provides an organizational chart creation method comprising: a node addition step for adding a new node; a node relationship drawing step in which the processor represents the relationship between the already installed nodes and the new node on the workspace; a node organizational chart storage step in which the processor stores the organizational chart represented by the nodes in a storage unit; an organizational chart identification step in which the processor associates the organizational chart with organizational identification information; an organizational chart reading and display step in which the processor receives input organizational identification information and displays the corresponding organizational chart on the workspace; and a department / project-specific accounting information output step in which the processor outputs accounting information for the project in the department based on the departmental identification information and project identification information of the department. The advantages in this case are the same as those in the first embodiment, so we will omit the explanation (see the effects of the invention described above). [Industrial applicability]

[0315] This approach can be applied not only to the construction industry but also to any work style where teams are flexibly changed for each project. [Explanation of Symbols]

[0316] 1. Organizational chart creation system 10 servers 12 Control Unit 122 processors 124 ROM 126 RAM 128 Timing section 14 Storage section 14a Program storage section 14b Data storage section 16 Communication Control Unit 18 Input / output section 20 devices 22 Control Unit 24 Memory section 26 Communication Control Unit 28 Input / output section 282 Input section 284 Output section 284a Display section UI-11 Menu Tab UI-12 Item-based menu UI-21 Organization Information Input Section UI-22 Organizational Chart Display Unit UI-23 Department Information Input Section UI-231 Department Search Button UI-24 Function Icons UI-251 Department Search Criteria Input Section UI-252 Department Search Button UI-253 Department Search Results List Display Section UI-254 Confirm button UI-261 Organization Search Criteria Input Section UI-262 Organization Search Button UI-263 Organization Search Results List Display Section UI-264 Confirm button UI-31 Construction Basic Information Input Section UI-32 Construction Information Tab UI-33 Construction Details Input Section UI-34 Function Icons UI-41 Invoice Basic Information Input Section UI-42 Invoice Function Icon UI-43 Accounting Information Input Section UI-431 Debit (credit) total part UI-44 Function Icons UI-51 Form Type Selection Section UI-52 Form Output Condition Input Section UI-53 Function Icons UI-61 Basic Information Display Section for Forms UI-62 Accounting Information List Display Unit UI-63 Ordered Construction Project List Display Section UI-64 Construction Project Profit Trends Display Section UI-65 Profit and loss information display section for each construction project UI-71 Construction Inquiry Condition Input Section UI-72 Construction Search Button UI-73 Construction List Display Unit P1 Organizational Chart Creation Program P12 Department Information Acquisition Program P14 Organizational Chart Drawing Program P16 Report Creation Program D1 Organizational Chart Creation Database D11 User Information Table D12 User Permissions Details Table D21 Organization Master D22 Department Master D23 Departmental Account Authority Master D31 Project (Construction) Master D41 Subject Master D42 Invoice Table

Claims

1. Computers, Organization information acquisition means for acquiring organizational information that includes the organization's organizational code or organizational name as organizational identification information. A means for acquiring departmental information that includes the department code or department name of a department constituting the aforementioned organization as departmental identification information. Project information acquisition means for acquiring project information that includes the project code or project name of a project in which the aforementioned department is involved as project identification information. A means for acquiring project accounting information to acquire accounting information for projects in which the aforementioned department is involved. A node addition means that adds a new node by a user's node addition operation, which is performed by specifying a node that corresponds to the department and is already installed in the workspace displayed on the computer's display unit. Node relationship drawing means for representing the relationship between the already placed nodes and the new nodes on the workspace, Node organizational diagram storage means for storing the organizational diagram represented by the aforementioned nodes in a storage unit, Organizational chart identification means for associating the organizational chart with organizational identification information, An organizational chart reading and display means that accepts input of organizational identification information and displays the corresponding organizational chart in the workspace, and A departmental / project-specific accounting information output means that outputs accounting information for the project in the department, based on the departmental identification information and the project identification information. An organizational chart creation program characterized by its function as such.

2. The node addition means is Input department code acquisition method to obtain the department code of a newly added node. A duplicate organizational code determination means for determining whether the department code of the newly added node is an existing one, (1) When the department code of the newly added node is an existing department code, an existing department addition means for adding a department corresponding to that department code, (2) If the department code of the newly added node is not an existing department code, a means for obtaining the department name of the newly added node, The organizational chart creation program according to claim 1, characterized by including the following:

3. The node addition means is In a workspace, a subordinate department node addition means allows a user to add a subordinate department to a node by specifying a node that corresponds to the department and is already installed. The organizational chart creation program according to claim 1, characterized in that it is the same as described above.

4. Furthermore, computers In a workspace, a node deletion means deletes a node by a user's node deletion operation, which specifies a node that corresponds to the department and is already installed. In a workspace, a node sorting means sorts the nodes contained in a node by department code order based on a user's node sorting operation, which is performed by specifying a node that corresponds to the department and is already installed. The organizational chart creation program according to claim 1, characterized in that it functions as such.

5. Furthermore, computers A means for outputting a breakdown of work-in-progress expenditures that outputs a breakdown of work-in-progress expenditures including at least the department information, the project information, the account titles, and the amounts of the said account titles. The organizational chart creation program according to claim 1, characterized in that it functions as such.

6. Furthermore, computers A means for outputting a list of ordered construction projects, which outputs a list of ordered construction projects including at least the departmental information, the project information, information about the client, information about the contract amount, and information about the construction period. The organizational chart creation program according to claim 1, characterized in that it functions as such.

7. Furthermore, computers A construction project project profit trend output means that outputs a construction project project profit trend table including at least the department information, project information, contract amount information, cost information, and profit information. The organizational chart creation program according to claim 1, characterized in that it functions as such.

8. Furthermore, computers A means for outputting a project-specific profit and loss management table that outputs a project-specific profit and loss management table including at least the department information, project information, construction period information, cost information, sales information, and profit information. The organizational chart creation program according to claim 1, characterized in that it functions as such.

9. Organization information acquisition unit that acquires organizational information including the organization's organizational code or organizational name as organizational identification information. A department information acquisition unit that acquires department information including the department code or department name of the departments constituting the aforementioned organization as department identification information. A project information acquisition unit that acquires project information including the project code or project name of the project in which the aforementioned department is involved as project identification information. Project Accounting Information Acquisition Unit, which acquires accounting information for projects in which the aforementioned department is involved. In the workspace displayed on the computer's display unit, a node addition unit adds a new node by specifying a node that corresponds to the department and is already installed, as performed by the user in a node addition operation. A node relationship drawing unit that represents the relationship between the already placed nodes and the new nodes on the workspace. A node organizational diagram storage unit that stores the organizational diagram represented by the aforementioned nodes in a storage unit. Organizational chart identification unit that associates the organizational chart with organizational identification information, An organizational chart reading and display unit that accepts input of organizational identification information and displays the corresponding organizational chart in the workspace, and A departmental / project-specific accounting information output unit outputs accounting information for a given project within a given department, based on the departmental identification information and project identification information of that department. An organizational chart creation system characterized by comprising the following features.

10. Organization information acquisition step: The processor acquires organization information that includes the organization's organization code or organization name as organizational identification information. A department information acquisition step in which the processor acquires department information including the department code or department name of the departments constituting the organization as department identification information. Project information acquisition step: The processor acquires project information that includes the project code or project name of the project in which the department is involved as project identification information. The processor performs a project accounting information acquisition step in which it acquires accounting information for projects in which the department is involved. The processor adds a new node in the workspace displayed on the computer's display unit by a user's node addition operation, which involves specifying a node that corresponds to the department and is already installed. The processor performs a node relationship drawing step in which it represents the relationship between the already placed nodes and the new nodes on the workspace. A node organizational diagram storage step in which the processor causes the organizational diagram represented by the nodes to be stored in a memory unit, The processor performs an organizational chart identification step of associating the organizational chart with organizational identification information. The processor receives input organizational identification information and displays the corresponding organizational chart in the workspace in an organizational chart reading and display step, and A department / project-specific accounting information output step in which the processor outputs accounting information for the relevant project within that department, based on the department identification information and project identification information of the department. A method for creating an organizational chart, characterized by being composed of the following.

Images