Project management device, project management method, and project management program

Abstract

To provide a project management device which can clearly associate expense fed to each work process of a project with sales.SOLUTION: A project management device comprises: registration means which creates contract specification data created for each order unit, sales schedule data created for each sales unit, and Job data created for each unit of the work process, according to operation of the business department staff; expense input means which creates expense data including an expense identification number for identifying expense, an occurrence date, project identification information, contract detailed identification information, sales schedule identification information, Job identification information, the type of the expense, and an expense money amount, according to the operation of the work department staff; and sales input means which creates sales data including a sales number, a sales date, the project identification information, the contract detailed identification information, the sales schedule identification information, and a sales money amount, according to the operation of the business department staff.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] The present invention relates to a project management device, a project management method, and a project management program.

Background Art

[0002] For example, conventionally, there is Patent Document 1 as a system for managing projects.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, Patent Document 1 does not describe anything regarding clearly associating the costs (costs) and sales input into each work process of the project.

[0005] The present invention has been made in view of the above, and an object thereof is to provide a project management device, a project management method, and a project management program capable of clearly associating the costs and sales input into each work process of the project.

Means for Solving the Problems

[0006] In order to solve the above-described problems and achieve the object, the present invention is a project management apparatus including a control unit, wherein the control unit, in response to an operation by a person in charge of the sales department, creates contract detail data including project identification information for identifying a project, contract detail identification information for identifying a contract, order receipt date, and order receipt amount, which are created for each order unit, and sales forecast data including project identification information, contract detail identification information, sales forecast identification information for identifying a sales forecast, sales forecast date, and sales forecast amount, which are created for each sales unit, and creates Job data including project identification information, contract detail identification information, sales forecast identification information, and Job identification information for identifying a Job, which are created for each unit of a work process, and registers the data in a storage area, and in response to an operation by a person in charge of the work department, creates expense data including an expense identification number for identifying an expense, occurrence date, project identification information, contract detail identification information, sales forecast identification information, Job identification information, type of expense, and expense amount, and registers the data in the storage area, and in response to an operation by a person in charge of the sales department, creates sales data including a sales number, sales date, project identification information, contract detail identification information, sales forecast identification information, and sales amount, and registers the data in the storage area.

[0007] Further, according to one aspect of the present invention, the expense data may include purchase data, daily report data, or settlement application data.

[0008] Further, according to one aspect of the present invention, the Job may include a Job related to a work process of requirement definition, basic design, or development.

[0009] Further, according to one aspect of the present invention, the control unit may further include a budget input means for creating budget data including budget identification information for identifying a budget, project identification information, contract detail identification information, sales forecast identification information, budget year and month, cost elements of an expense, and budget amount, and registering the data in the storage area.

[0010] Further, according to one aspect of the present invention, the control unit may further include a profit and loss statement creating means for creating and outputting a profit and loss statement including planned and actual sales and planned and actual cost elements for each fiscal year and month in units of projects, contract details, or planned sales based on the planned sales data, budget data, cost data, and sales data registered in the storage area.

[0011] In addition, in order to solve the above-described problems and achieve the object, the present invention is a project management method executed by an information processing apparatus including a control unit, and in the control unit, in response to an operation by a person in charge of the sales department, project identification information for identifying a project, contract detail identification information for identifying a contract, order date, and contract detail data including an order amount created for each order unit, project identification information, contract detail identification information, sales plan identification information for identifying a sales plan, sales plan date, and sales plan data including a sales plan amount created for each sales unit, and project identification information, contract detail identification information, sales plan identification information, and Job data including Job identification information for identifying a Job created for each unit of work process are created and registered in a storage area; a cost input step of creating cost data including a cost identification number for identifying a cost, a generation date, project identification information, contract detail identification information, sales plan identification information, Job identification information, a type of cost, and a cost amount in response to an operation by a person in charge of the work department and registering the cost data in the storage area; and a sales input step of creating sales data including a sales number, a sales date, project identification information, contract detail identification information, sales plan identification information, and a sales amount in response to an operation by a person in charge of the sales department and registering the sales data in the storage area.

[0012] In addition, in order to solve the above-described problems and achieve the object, the present invention is a project management program for causing an information processing apparatus including a control unit to execute. In the control unit, according to the operation of the person in charge of the sales department, project identification information for identifying a project, contract detail identification information for identifying a contract, order receipt date, and contract detail data including the order receipt amount created for each order receipt unit, and project identification information created for each sales unit, contract detail identification information, sales plan identification information for identifying a sales plan, sales plan date, and sales plan data including the sales plan amount, and project identification information, contract detail identification information, sales plan identification information, and Job data including Job identification information for identifying a Job created for each unit of a work process are created and registered in a storage area. A registration step, a cost input step of creating cost data including a cost identification number for identifying a cost, a generation date, project identification information, contract detail identification information, sales plan identification information, Job identification information, cost type, and cost amount according to the operation of the person in charge of the work department and registering the cost data in the storage area, and a sales input step of creating sales data including a sales number, a sales date, project identification information, contract detail identification information, sales plan identification information, and sales amount according to the operation of the person in charge of the sales department and registering the sales data in the storage area. It is characterized in that it is a project management program for causing the above to be executed.

Effect of the Invention

[0013] According to the present invention, there is an effect that it becomes possible to clearly associate the costs and sales input into each work process of a project.

Brief Description of the Drawings

[0014]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

[0015] Embodiments of the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to these embodiments. Also, in this specification and the claims, known techniques and well-known techniques are incorporated by reference, and descriptions of known techniques and well-known techniques may be omitted.

[0016] [1. Overview] For example, in the IT industry, for a single project, the association between sales and costs is essential in accounting. However, there are no unified rules for process management, and each company manages the breakdown at the granularity they desire (in units of WBS (Work Breakdown Structure)). The sales and technical (work) positions are divided, and in many cases, it is not clear which sales the members of the technical positions are linked to for each work process (for example, in the case of a system construction project, work processes such as requirement definition, basic design, and development). The association between the costs (expenses) invested in each work process and sales is not clearly defined, which poses an accounting issue.

[0017] Therefore, the project management device of this embodiment can clearly associate the costs (expenses) invested in each work process of a project with sales. As a result, members of the technical positions who are unaware of the sales contracts can also correctly invest costs. In addition, budget and actual management at each work process level, budget and actual management for each contract unit, and budget and actual management for the entire project can be achieved by correctly associating sales and costs.

[0018] The outline of the project management device of this embodiment will be described. FIG. 1 shows the correlation diagram of project data - contract detail data - sales forecast data - Job data of this embodiment. In FIG. 1, the project data, contract detail data, sales forecast data, and Job data are associated. The sales forecast data is the minimum unit of revenue and expenditure. The Job data is the minimum unit of cost management.

[0019] The functional outline of the project management device of this embodiment is as follows. (1) Input project data for the entire project. (2) Register contract detail data associated with the project, and further input sales forecast data associated with the contract detail data and Job data (used for associating costs) associated with the sales forecast data. (3) Register a budget for each Job data (optional). (4) When costs are incurred, register them in association with the Job data created above during purchase input, settlement application, and daily report input. (5) When sales are recorded, register them in association with the sales schedule data created above during sales registration.

[0020] The project management device of this embodiment is widely applicable to industries such as IT media that conduct business in a project management type.

[0021] [2. Configuration] An example of the configuration of the project management device according to this embodiment will be described with reference to the drawings.

[0022] FIG. 1 is a block diagram showing an example of the project management device according to this embodiment. The project management device 100 is a workstation, a commercially available desktop personal computer, or the like.

[0023] The project management device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each unit included in the project management device 100 is communicably connected via an arbitrary communication path.

[0024] The communication interface unit 104 communicably connects the project management device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via a communication line. Here, the network 300 has a function of communicably connecting the project management device 100 with the server 200, the terminal 400, etc., and is, for example, the Internet, a LAN (Local Area Network), or the like. Thereby, the communication interface unit 104 is configured to be able to perform data communication with the terminal 400, etc. and the server 200 via the network 300. The terminal 400, etc. are, for example, the terminals of the persons in charge of the sales department, the terminals of the persons in charge of the work (technology) department, the terminals of the persons in charge of the purchasing department, the terminals of the managers, etc. The project management device 100 and the terminal 400, etc. are configured to be able to perform data communication via the network 300.

[0025] An input device 112 and an output device 114 are connected to the input / output interface unit 108. For the output device 114, in addition to a monitor (including a home TV), a speaker and a printer can be used. For the input device 112, in addition to a keyboard, a mouse, and a microphone, a monitor that cooperates with the mouse to realize a pointing device function can be used. In the following, the output device 114 may be described as the monitor 114, and the input device 112 may be described as the keyboard 112 or the mouse 112.

[0026] Various databases, tables, files, etc. are stored in the storage unit 106. A computer program for giving commands to the CPU (Central Processing Unit) to perform various processes in cooperation with the OS (Operating System) is recorded in the storage unit 106. As the storage unit 106, for example, a memory device such as a RAM (Random Access Memory)·ROM (Read Only Memory), a fixed disk device such as a hard disk, a floppy disk, and an optical disk can be used.

[0027] In addition, this storage unit 106 stores a procurement product master 106a, project data, contract detail data, sales forecast data, Job data, budget data, order data, procurement data, settlement application data, and expense data such as daily report data, and sales data, etc. FIG. 3 is a diagram showing a configuration example of the procurement product master 106a.

[0028] As shown in FIG. 3, the procurement product master 106a can be composed of a table or the like that registers by associating procurement products (here, products include services, and "products" shall mean products and / or services) with cost elements. In the example shown in the figure, the first row shows the procurement product "requirement definition" and the cost element "labor cost", and the second row shows the procurement product "basic design" and the cost element "outsourcing cost". The procurement product master 106a is referred to when calculating the cost elements corresponding to the procurement products when creating a project income and expenditure statement.

[0029] The project data may include project identification information (project NO and / or project name) for identifying the project, etc.

[0030] The contract detail data may include project identification information (project NO and / or project name), contract detail information (contract detail NO and / or contract detail name) for identifying the contract, order receipt date, order receipt amount, etc.

[0031] The sales forecast data may include project identification information (project NO and / or project name), contract detail identification information (contract detail NO and / or contract detail name), sales forecast NO for identifying the sales forecast, sales forecast date, sales forecast amount, remarks, etc.

[0032] The Job data may include project identification information (project NO and / or project name), contract identification information (contract detail NO and / or contract detail name), sales forecast identification information (sales forecast NO), Job identification information (Job NO and / or Job name) for identifying the Job, etc.

[0033] Budget data is composed of budget header data and budget detail data. The budget header data may include a budget number, a project number, a contract detail number, a planned sales number, a Job number, a budget name, etc. The budget detail data may include a budget number, a budget detail SEQ, a budget year and month, a cost element, a budget amount, etc.

[0034] Purchase order data is composed of purchase order header data and purchase order detail data. The purchase order header data may include a purchase order number, a purchase order date, a planned procurement date, etc. The purchase order detail data may include a purchase order number, a purchase order detail SEQ, a project number, a contract detail number, a planned sales number, a Job number, a procurement item, a purchase order amount, etc.

[0035] Expense data may include an expense identification number (e.g., a purchase order number) for identifying the expense, a posting date (e.g., a purchase date), project identification information, contract detail identification information, planned sales identification information, Job identification information, a type of expense (e.g., a procurement item), an expense amount (e.g., a purchase amount), etc.

[0036] Among the expense data, the purchase data is composed of purchase header data and purchase detail data. The purchase header data may include a purchase order number, a purchase date, a purchase order number, etc. The purchase detail data may include a purchase order number, a purchase detail SEQ, a purchase order number, a purchase order detail SEQ, a project number, a contract detail number, a planned sales number, a Job number, a procurement item, a purchase amount, etc.

[0037] Sales data is composed of sales header data and sales detail data. The sales header data may include a sales number, a sales date, a project number, a contract detail number, etc. The sales detail data may include a sales number, a sales detail SEQ, a project number, a contract detail number, a planned sales number, a sales amount, etc.

[0038] Returning to FIG. 2, the control unit 102 is a CPU or the like that comprehensively controls the project management device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs defining various processing procedures, and required data, and executes various information processes based on these stored programs.

[0039] The control unit 102 is configured to be able to access the purchased item master 106a, project data, contract detail data, sales plan data, Job (Job) data, budget data, purchase order data, expense data (purchase data, settlement application data, daily report data, etc.), sales data, etc. stored in the storage unit 106. Note that the purchased item master 106a, project data, contract detail data, sales plan data, Job data, budget data, purchase order data, expense data (purchase data, settlement application data, daily report data, etc.), sales data, etc. may be provided in other locations (for example, the server 200), as long as the control unit 102 can access them.

[0040] Functionally conceptually, the control unit 102 includes a project registration unit 102a, a contract detail registration unit 102b, a budget registration unit 102c, a purchase order input unit 102d, a purchase input unit 102e, a settlement application unit 102f, a daily report input unit 102g, a cost calculation unit 102h, a sales input unit 102i, a project revenue and expenditure management unit 102j, a master maintenance unit 102k, and a screen display control unit 102l.

[0041] The purchase input unit 102e, the settlement application unit 102f, and the daily report input unit 102g are collectively referred to as expense input means for inputting expense data (for example, purchase data, settlement application data, daily report data). The expense input means creates expense data including an expense identification number, a generation date, project identification information, contract detail identification information, sales plan identification information, Job identification information, expense type, and expense amount for identifying an expense in response to an operation by a person in charge of the work unit, and registers it in the storage unit 106.

[0042] The project registration unit 102a provides a project registration screen in response to an access from, for example, the terminal 400 of a person in charge of the sales department, and creates project data according to an operation of the person in charge of the sales department on the project registration screen and registers it in the storage unit 106.

[0043] The contract details registration unit 102b provides a contract details registration screen in response to an access from, for example, the terminal 400 of a person in charge of the sales department, and creates, for each order unit, project identification information for identifying a project, contract details identification information for identifying a contract, order date, contract details data including the order amount, and for each sales unit, project identification information, contract details identification information, sales plan identification information for identifying a sales plan, sales plan date, sales plan data including the sales plan amount, and for each unit of work process, project identification information, contract details identification information, sales plan identification information, Job data including Job identification information for identifying a Job. A Job may include a Job related to a work process of requirement definition, basic design, or development. The created data is registered in the storage unit 106.

[0044] The budget registration unit 102c provides a budget registration screen in response to an access from, for example, the terminal 400 of a person in charge of the sales department, and creates budget data including budget identification information for identifying a budget, project identification information, contract details identification information, sales plan identification information, budget year and month, cost elements of expenses, and budget amount according to an operation of the person in charge of the sales department on the budget registration screen and registers it in the storage unit 106.

[0045] The purchase order input unit 102d provides a purchase order input screen in response to an access from, for example, the terminal 400 of a person in charge of the sales department, and creates purchase order data according to an operation of the person in charge of the sales department on the purchase order input screen and registers it in the storage unit 106.

[0046] The procurement input section 102e provides a procurement input screen in response to access from, for example, the terminal 400 of a person in charge in the sales department or the terminal 400 of a person in charge in the purchasing department, and creates procurement data and registers it in the storage section 106 according to operations of the person in charge in the sales department or the person in charge in the purchasing department on the procurement input screen.

[0047] The settlement application section 102f provides a settlement application screen in response to access from, for example, the terminal 400 of a person in charge in the work section or the terminal 400 of a person in charge in the purchasing department, and creates settlement application data and registers it in the storage section 106 according to operations of the person in charge in the sales department or the person in charge in the purchasing department on the settlement application screen.

[0048] The daily report input section 102g provides a daily report input screen in response to access from, for example, the terminal 400 of a person in charge in the work section, and creates daily report data and registers it in the storage section 106 according to operations of the person in charge in the work section on the daily report input screen.

[0049] The cost calculation section 102h calculates the cost for each Job (JobNO) of the project based on the daily report data registered in the storage section 106 and registers it in the storage section 106 (for example, referring to a master (not shown) storing the unit price per hour of the worker, calculates the cost for each worker by working hours × unit price).

[0050] The sales input section 102i provides a sales input screen in response to access from, for example, the terminal 400 of a person in charge in the sales department, and creates sales data including a sales number, a sales date, project identification information, contract detail identification information, sales plan identification information, and a sales amount and registers it in the storage section 106 according to operations of the person in charge in the sales department on the sales input screen.

[0051] The project revenue and expenditure management unit 102j provides a revenue and expenditure management screen in response to access from, for example, the terminal 400 of the manager. Based on contract detail data, sales forecast data, budget data, expense data, sales data, etc. registered in the storage unit 106 in response to operations of the manager on the revenue and expenditure management screen, etc., it creates and displays / outputs a revenue and expenditure statement including the planned and actual sales and the planned and actual cost elements on a monthly accounting basis in units of projects, contract details, or sales forecasts.

[0052] The master maintenance unit 102k is for making settings such as data input, addition, change, update, etc. to the purchased goods master 106a in response to operations of the operator on a master maintenance screen (not shown).

[0053] The screen display control unit 102l controls the display and input reception of various screens (for example, master maintenance screen, project registration screen, contract detail screen, budget registration screen, purchase order input screen, purchase input screen, settlement application registration screen, daily report input screen, sales input screen, revenue and expenditure management screen, etc.).

[0054] [3. Specific Example] A specific example of the processing of the control unit 102 of the project management device 100 according to the present embodiment will be described with reference to FIGS. 2 to 14.

[0055] (3-1. Overall Processing) FIG. 4 is a flowchart for explaining the outline of the overall processing flow of the control unit 102 of the project management device 100. With reference to FIG. 4, the outline of the overall processing flow of the control unit 102 of the project management device 100 will be described.

[0056] In FIG. 4, the project registration unit 102a executes a project registration process (step S1). Specifically, in the project registration process, the project registration unit 102a provides a project registration screen in response to access from, for example, the terminal 400 of the person in charge of the sales department, and creates project data and registers it in the storage unit 106 in response to operations of the person in charge of the sales department on the project registration screen.

[0057] The contract details registration unit 102b executes a contract details registration process (step S2). Specifically, in the contract details registration process, the contract details registration unit 102b provides a contract details registration screen in response to an access from, for example, the terminal 400 of a person in charge in the sales department, and creates contract details data including project identification information for identifying a project, contract details identification information for identifying a contract, order receipt date, and order receipt amount created for each order receipt unit, and sales forecast data including project identification information, contract details identification information, sales forecast identification information for identifying a sales forecast, sales forecast date, and sales forecast amount created for each sales unit, and Job data including project identification information, contract details identification information, sales forecast identification information, and Job identification information for identifying a Job created for each unit of a work process, in response to an operation of the person in charge in the sales department on the contract details registration screen, and registers the data in the storage unit 106.

[0058] The budget registration unit 102c executes a budget registration process (step S3). Specifically, the budget registration unit 102c provides a budget registration screen in response to an access from, for example, the terminal 400 of a person in charge in the sales department, and creates budget data including budget identification information for identifying a budget, project identification information, contract details identification information, sales forecast identification information, Job identification information (JobNO), budget year and month, cost elements of expenses, and budget amount in response to an operation of the person in charge in the sales department on the budget registration screen, and registers the data in the storage unit 106. Here, a budget is allocated to each work (JobNO).

[0059] The purchase order input unit 102d executes a purchase order input process (step S4). Specifically, in the purchase order input process, the purchase order input unit 102d provides a purchase order input screen in response to an access from, for example, the terminal 400 of a person in charge in the sales department, and creates purchase order data in response to an operation of the person in charge in the sales department on the purchase order input screen, and registers the data in the storage unit 106.

[0060] The procurement input section 102e executes procurement input processing (step S5). Specifically, in the procurement input processing, the procurement input section 102e provides a procurement input screen in response to access from, for example, the terminal 400 of the person in charge in the sales department or the terminal 400 of the person in charge in the purchasing department, and creates procurement data and registers it in the storage section 106 according to operations of the person in charge in the sales department or the person in charge in the purchasing department on the procurement input screen. Here, costs due to procurement are input for each job (JobNO).

[0061] The settlement application section 102f executes settlement application processing (step S6). Specifically, in the settlement application processing, the settlement application section 102f provides a settlement application screen in response to access from, for example, the terminal 400 of the person in charge in the work department or the terminal 400 of the person in charge in the purchasing department, and creates settlement application data and registers it in the storage section 106 according to operations of the person in charge in the sales department or the person in charge in the purchasing department on the settlement application screen. Here, costs due to settlement applications are input for each job (JobNO).

[0062] The daily report input section 102g executes daily report input processing (step S7). Specifically, in the daily report input processing, the daily report input section 102g provides a daily report input screen in response to access from, for example, the terminal 400 of the person in charge in the work department, and creates daily report data and registers it in the storage section 106 according to operations of the person in charge in the work department on the daily report input screen.

[0063] The cost calculation section 102h executes cost calculation processing (step S8). Specifically, the cost calculation section 102h calculates the costs for each job (JobNO) of the project based on the daily report data registered in the storage section 106 and registers it in the storage section 106. Here, costs are calculated according to the man-hours (working hours of the worker) of the daily report data, and costs are input for each job (JobNO).

[0064] The sales input unit 102i executes a sales input process (step S9). Specifically, in the sales input process, the sales input unit 102i provides a sales input screen in response to an access from, for example, the terminal 400 of a person in charge in the sales department, and creates sales data including a sales number, a sales date, project identification information, contract detail identification information, sales plan identification information, and a sales amount according to an operation of the person in charge in the sales department on the sales input screen, and registers the sales data in the storage unit 106. Here, the sales amount is input for each sales plan (sales plan NO).

[0065] The project revenue and expenditure management unit 102j executes a project revenue and expenditure statement process (step S10). Specifically, in the project revenue and expenditure statement process, the project revenue and expenditure management unit 102j provides a revenue and expenditure management screen in response to an access from, for example, the terminal 400 of a manager, and creates and displays / prints out a revenue and expenditure statement including the planned and actual sales and the planned and actual cost elements for each fiscal year and month in units of projects, contract details, or sales plans based on the contract detail data, sales plan data, budget data, expense data, and sales data registered in the storage unit 106 according to an operation of the manager on the revenue and expenditure management screen etc.

[0066] (3-2. Sample Data) With reference to FIGS. 5 to 14, a specific example of the processing of the control unit 102 of the project management device 100 will be described. FIGS. 5 to 14 are diagrams for explaining a specific example of the processing of the control unit 102 of the project management device 100. In the following example, as an example of inputting expenses, the case of inputting purchase expenses will be described, and the description of the case of inputting expenses by settlement application or daily report input will be omitted.

[0067] (S1: Project Registration Process) With reference to FIG. 5, a specific example of the project registration process will be described. In the project registration process, project information is registered. The project registration unit 102a provides a project registration screen in response to an access from, for example, the terminal 400 of a person in charge in the sales department, and inputs project data and registers it in the storage unit 106 according to an operation of the person in charge in the sales department on the project registration screen etc.

[0068] Project data is data for managing the entire project period and the main salesperson, billing destination, and customer. FIG. 5 is a diagram showing an example (partial) of project data. Project data includes items such as a project number and a project name. In the example shown in the figure, the first row has a project number of "PJ0001" and a project name of "System Construction Project".

[0069] (S2: Contract Detail Registration Process) With reference to FIGS. 6 and 7, a specific example of the contract detail registration process will be described. The contract detail registration unit 102b provides a contract detail registration screen, for example, in response to an access from the terminal 400 of the sales department staff, and creates, for each order unit, project identification information for identifying a project, contract detail identification information for identifying a contract, order date, and contract detail data including the order amount, and for each sales unit, project identification information, contract detail identification information, sales schedule identification information for identifying a sales schedule, sales schedule date, and sales schedule data including the sales schedule amount, and for each unit of work process, project identification information, contract detail identification information, sales schedule identification information, and job data including job identification information for identifying a job, and registers them in the storage unit 106.

[0070] The contract detail data is a unit representing one order and is data for managing business type, salesperson, management person, billing destination, customer, sales product, sales quantity, sales amount, etc. The project data and the contract detail data have a one-to-N relationship and are linked by the project number.

[0071] FIG. 6(A) is a diagram showing an example (partial) of contract details data. In the example shown in this figure, the contract details data includes items such as project NO, contract details NO, order receipt date, contract details name, and order receipt amount. In the example shown in this figure, the first row shows project NO "PJ0001", contract details NO "0001", order receipt date "2023 / 04 / 15", contract details name "Construction and introduction of project management system", order receipt amount "￥10,000,000", and the second row shows project NO "PJ0001", contract details NO "0002", order receipt date "2023 / 04 / 25", contract details name "Construction and introduction of accounting system", order receipt amount "￥20,000,000".

[0072] The sales forecast data is a unit representing one sales unit and is data for managing the sales forecast amount, sales forecast date, and sales status. The contract details data and the sales forecast data have a one-to-N relationship and are linked by the project NO and the contract details NO.

[0073] FIG. 6(B) is a diagram showing an example (partial) of sales forecast data. The sales forecast data includes items such as project NO, contract details NO, sales forecast NO, sales forecast date, sales forecast amount, remarks, etc. In the example shown in this figure, the first row shows project NO "PJ0001", contract details NO "0001", sales forecast NO "001", sales forecast date "2023 / 09 / 20", sales forecast amount "￥10,000,000", remarks "Construction and introduction of project management system_sales (batch)", and the second row shows project NO "PJ0001", contract details NO "0002", sales forecast NO "002", sales forecast date "2023 / 07 / 20", sales forecast amount "￥20,000,000", remarks "Construction and introduction of accounting system_sales in July 2023".

[0074] Job data is a unit representing one work unit and is data for managing the Job name, person in charge, and work reception date. All cost information such as purchases and daily reports will be linked to the Job. The sales forecast data and the Job data have a one-to-N relationship and are linked by the project NO, contract details NO, and sales forecast NO.

[0075] FIG. 6(C) is a diagram showing an example (partial) of Job data. The Job data includes items such as project NO, contract detail NO, sales plan NO, Job NO, Job name, etc. The first line shows project NO "PJ0001", contract detail NO "0001", sales plan NO "001", Job NO "001", Job name "requirement definition", and the second line shows project NO "PJ0001", contract detail NO "0001", sales plan NO "001", Job NO "002", Job name "basic design".

[0076] FIG. 7 shows a relationship diagram of project NO, contract detail NO, sales plan NO, and Job NO. In the example shown in the figure, for example, contract detail NOs "0001" and "0002" are associated with project NO "PJ0001". For example, sales plan NO "001" is associated with contract detail NO "0001", and Job NOs "001" and "002" are associated with sales plan NO "001".

[0077] (S3: Budget registration process) Referring to FIG. 8, a specific example of the budget registration process will be described. The budget registration unit 102c provides a budget registration screen, for example, in response to an access from the terminal 400 of the person in charge of the sales department, and creates budget data including budget identification information, project identification information, contract detail identification information, sales plan identification information, Job identification information, budget year and month, cost elements of expenses, and budget amount in response to operations of the person in charge of the sales department on the budget registration screen, and registers it in the storage unit 106. Here, costs are input for each operation (Job NO).

[0078] The budget data is composed of budget header data and budget detail data. The budget header data is data for managing information such as registration date, budget name, project NO, contract detail NO, sales plan NO, Job NO (for cost association), etc. The budget detail data is data for managing information such as budget year and month, cost elements, budget amount, etc.

[0079] Here, in the purchase item master 106a (see Fig. 3), since the "requirement definition" of the purchase item corresponds to the cost element "labor cost" and the "basic design" of the purchase item corresponds to the cost element "outsourcing cost", the case where the work of "requirement definition" is done in-house and the work of "basic design" is outsourced to another company will be explained.

[0080] Fig. 8(A) is a diagram showing an example (partial) of budget header data. The budget header data includes items such as budget NO, project NO, contract detail NO, sales forecast NO, JobNO, budget name, etc. In the example shown in the figure, the first row has budget NO "YOS0001", project NO "PJ0001", contract detail NO "0001", sales forecast NO "001", JobNO "001", budget name "Project management system construction and introduction - requirement definition", and the second row has budget NO "YOS0002", project NO "PJ0001", contract detail NO "0001", sales forecast NO "001", JobNO "002", budget name "Project management system construction and introduction - basic design".

[0081] Fig. 8(B) is a diagram showing an example (partial) of budget detail data. The budget detail data includes items such as budget NO, budget detail SEQ, budget year / month, cost element, budget amount, etc. In the example shown in the figure, the first row has budget NO "YOS0001", budget detail SEQ "001", budget year / month "2023 / 09", cost element "labor cost", budget amount "￥500,000", and the second row has budget NO "YOS0002", budget detail SEQ "002", budget year / month "2023 / 09", cost element "outsourcing cost", budget amount "￥2,000,000".

[0082] (S4: Purchase order input process) Referring to Fig. 4, a specific example of the purchase order input process will be explained. The purchase order input unit 102d provides a purchase order input screen, for example, in response to an access from the terminal 400 of the person in charge in the sales department, and creates purchase order data and registers it in the storage unit 106 according to the operations of the person in charge in the sales department on the purchase order input screen.

[0083] The purchase order data is composed of purchase order header data and purchase order line item data. The purchase order header data is data for managing information such as the order date, supplier, payee, and scheduled purchase date. The purchase order line item data is data mainly for managing purchased goods, quantity, unit price, amount, etc.

[0084] Figure 9(A) is a diagram showing a data example (part) of the purchase order header data. The purchase order header data has items such as a purchase order number, order date, and scheduled purchase date. In the example shown in the figure, the first row has a purchase order number of "HAC0001", an order date of "2023 / 05 / 10", and a scheduled purchase date of "2023 / 09 / 25", and the second row has a purchase order number of "HAC0002", an order date of "2023 / 05 / 10", and a scheduled purchase date of "2023 / 05 / 20".

[0085] Figure 9(B) is a diagram showing a data example (part) of the purchase order line item data. The purchase order line item data has items such as a purchase order number, purchase order line item SEQ, project NO, contract line item NO, projected sales NO, JobNO, purchased goods, and order amount. In the example shown in the figure, the first row has a purchase order number of "HAC0001", a purchase order line item SEQ of "001", a project NO of "PJ0001", a contract line item NO of "0001", a projected sales NO of "001", a JobNO of "001", purchased goods of "requirement definition", and an order amount of "￥600,000", and the second row has a purchase order number of "HAC0001", a purchase order line item SEQ of "002", a project NO of "PJ0001", a contract line item NO of "0001", a projected sales NO of "001", a JobNO of "002", purchased goods of "basic design", and an order amount of "￥2,500,000".

[0086] Figure 9(C) shows a data example of the purchased goods master 106b. The purchased goods "requirement definition" has a cost element of "labor cost", and the purchased goods "basic design" has a cost element of "outsourcing cost".

[0087] (S5: Purchase input process) Referring to FIG. 10, a specific example of the purchase input process will be described. The purchase input unit 102e provides a purchase input screen, for example, in response to access from the terminals 400 of the sales department staff or the terminals 400 of the purchasing department staff, and creates purchase data according to the operations of the sales department staff or the purchasing department staff on the purchase input screen and registers it in the storage unit 106.

[0088] The purchase data is composed of purchase header data and purchase detail data. The purchase header data is data for managing the purchase date, supplier, payee, closing date, scheduled payment date, etc. The purchase detail data is data mainly for managing purchased goods, quantity, unit price, amount, etc.

[0089] Here, the case of recording expenses for purchases will be described as follows. In addition to this, there are also settlement applications and daily report data that are subject to cost calculation processing for expense recording, but their descriptions will be omitted. For the project NO - contract detail NO: PJ0001 - 0001 (introduction of project management system construction), the case of recording expenses in September after receiving the order in April will be described. Also, for the project NO - contract detail NO: PJ0001 - 0002 (introduction of accounting system construction), the case of sequentially recording expenses in May, June, July, August, and September after receiving the order in April will be described.

[0090] FIG. 10(A) is a diagram showing a data example (part) of the purchase header data. The purchase header data includes items such as purchase number, purchase date, and order number. In the example shown in the figure, the first row has a purchase number of "SII0001", a purchase date of "2023 / 09 / 25", and an order number of "HAC0001", and the second row has a purchase number of "SII0002", a purchase date of "2023 / 05 / 20", and an order number of "HAC0002".

[0091] FIG. 10(B) is a diagram showing a data example (part) of purchase details data. The purchase details data includes items such as purchase number, purchase details SEQ, order number, order details SEQ, project NO, contract details NO, sales forecast NO, JobNO, purchased goods, and purchase amount. In the example shown in the figure, for the first line, the purchase number is "SII0001", the purchase details SEQ is "001", the order number is "HAC0001", the order details SEQ is "001", the project NO is "PJ0001", the contract details NO is "0001", the sales forecast NO is "001", the JobNO is "001", the purchased goods is "requirement definition", and the purchase amount is "￥600,000". For the second line, the purchase number is "SII0001", the purchase details SEQ is "002", the order number is "HAC0001", the order details SEQ is "002", the project NO is "PJ0001", the contract details NO is "0001", the sales forecast NO is "001", the JobNO is "002", the purchased goods is "basic design", and the purchase amount is "￥2,500,000".

[0092] (S9: Sales input processing) Referring to FIG. 11, a specific example of the sales input processing will be described. The sales input unit 102i provides a sales input screen, for example, in response to an access from the terminal 400 of the person in charge of the sales department, and creates sales data including a sales number, a sales date, project identification information, contract details identification information, sales forecast identification information, and a sales amount according to an operation of the person in charge of the sales department on the sales input screen, and registers the sales data in the storage unit 106.

[0093] The sales data is composed of sales header data and sales details data. The sales header data is data for managing the sales date, the billing destination, the customer, the sales goods, the sales quantity, the sales amount, the billing scheduled date, the collection scheduled date, etc. The sales details data is data for managing the breakdown of the sales slip, such as the sales amount and the sales consumption tax.

[0094] Here, the sales are recorded as follows. For Project No.-Contract Detail No.: PJ0001-0001, the case where the order is received in April and the sales are recorded in September will be explained. For Project No.-Contract Detail No.: PJ0001-0002, the case where the sales are sequentially recorded in August and September after the order is received in April will be explained (for example, the planned sales in July were not recognized as sales at the time of July and were recorded in September).

[0095] Figure 11(A) is a diagram showing a data example (partial) of sales header data. The sales header data includes items such as a sales number, a sales date, a project number, and a contract detail number. In the example shown in the figure, the first row has a sales number of "URI0001", a sales date of "2023 / 09 / 15", a project number of "PJ0001", and a contract detail number of "0001". The second row has a sales number of "URI0002", a sales date of "2023 / 08 / 20", a project number of "PJ0001", and a contract detail number of "0002".

[0096] Figure 11(B) is a diagram showing a data example (partial) of sales detail data. The sales detail data includes items such as a sales number, a sales detail SEQ, a project number, a contract detail number, a planned sales number, and a sales amount. In the example shown in the figure, the first row has a sales number of "URI0001", a sales detail SEQ of "001", a project number of "PJ0001", a contract detail number of "0001", a planned sales number of "001", and a sales amount of "￥10,000,000". The second row has a sales number of "URI0002", a sales detail SEQ of "002", a project number of "PJ0001", a contract detail number of "0002", a planned sales number of "003", and a sales amount of "￥8,000,000".

[0097] (S10: Project Profit and Loss Statement Processing) With reference to FIGS. 12 to 14, a specific example of project profit and loss statement processing will be described. The project profit and loss management unit 102j provides a profit and loss management screen, for example, in response to an access from the terminal 400 of the manager. Based on the project data, contract detail data, sales forecast data, budget data, expense data, and sales data registered in the storage unit 106 according to the operations of the manager on the profit and loss management screen, etc., it creates and displays a project profit and loss statement including the planned and actual sales and the planned and actual cost elements for each fiscal year and month in units of projects, contract details, or sales forecasts. The project profit and loss statement is for checking the profit and loss and the comparison between the planned and actual figures from sales, cost, and budget.

[0098] In the case of the project unit, a profit and loss statement for each project number is created using the project number as the key. In the case of the contract detail unit, a profit and loss statement for each project number - contract detail number is created using the project number - contract detail number as the key. In the case of the sales forecast unit, a profit and loss statement for each project number - contract detail number - sales forecast number is created using the project number - contract detail number - sales forecast number as the key.

[0099] FIG. 12 is a diagram showing an example of a project profit and loss statement in project units. FIG. 13 is a diagram showing an example of a project profit and loss statement in contract detail units. FIG. 14 is a diagram showing an example of the data and calculation method (item transfer table) used as the basis for creating the project profit and loss statement. The project profit and loss statement is created according to the transfer item table shown in FIG. 14.

[0100] Here, the case of creating and checking the profit and loss statements for the project unit (PJ0001) and the contract detail unit (PJ0001 - 0002) among the data registered above will be described. The example of the sales forecast unit is omitted from the description.

[0101] Figure 12 shows an example of a project income and expenditure statement in project units, showing an example of the income and expenditure statement for project No. "PJ0001" and project name "System Construction Project". In the income and expenditure statement, the horizontal axis represents the fiscal year and month, and the total, and the vertical axis represents the order received, sales (planned, actual), labor costs (planned, actual), outsourcing costs (planned, actual), cost of sales, gross profit, and gross profit rate. Using project No. "PJ0001" as the key, according to the transfer item table shown in Figure 14, a project income and expenditure statement is created. For each fiscal year and month, for "order received", the received amount of the contract details data is obtained; for "sales (planned)", the planned sales amount of the sales plan data is obtained; for "sales (actual)", the sales amount of the sales details data is obtained; for "labor costs (planned)", the budget amount of the cost element = labor costs in the budget details data is obtained; for "labor costs (actual)", the purchase amount of the cost element = labor costs (refer to purchase product master 106a and obtain the cost element using the purchased product as the key) in the purchase details data is obtained; for "outsourcing costs (planned)", the budget amount of the cost element = outsourcing costs in the budget details data is obtained; for "outsourcing costs (actual)", the purchase amount of the cost element = outsourcing costs in the purchase details data is obtained; for "cost of sales", the purchase amount of the purchase details data is obtained; for "gross profit", it is calculated as the sales amount of the sales details data - the purchase amount of the purchase details data; for "gross profit rate", it is calculated as (sales amount of the sales details data - purchase amount of the purchase details data) / sales amount of the sales details data × 100.

[0102] Figure 13 shows an example of a project income and expenditure statement in contract detail units, showing an example of the income and expenditure statement for project No. "PJ0001", project name "System Construction Project" - contract detail No. "0002", and contract detail name "Accounting System Construction and Introduction". Using project No. "PJ0001" - contract detail No. "0002" as the key, according to the transfer item table shown in Figure 14, a project income and expenditure statement is created. The details of the creation method are almost the same as those in Figure 12, so a detailed explanation is omitted.

[0103] As described above, according to the present embodiment, in response to the operation of the person in charge of the sales department, project identification information for identifying a project, contract detail identification information for identifying a contract, order receipt date, and contract detail data including the order receipt amount, which are created for each order unit, and project identification information, contract detail identification information, sales forecast identification information for identifying a sales forecast, sales forecast date, and sales forecast data including the sales forecast amount, which are created for each sales unit, and project identification information, contract detail identification information, sales forecast identification information, and Job data including Job identification information for identifying a Job, which are created for each unit of work process, are created by the contract detail registration unit 102b and registered in the storage unit 106. In response to the operation of the person in charge of the work department, cost identification number for identifying a cost, occurrence date, project identification information, contract detail identification information, sales forecast identification information, Job identification information, type of cost, and cost data including the cost amount are created and registered in the storage unit 106 by the cost input means (for example, purchase input unit 102e, settlement application unit 102f, daily report input unit 102g). In response to the operation of the person in charge of the sales department, sales data including a sales number, sales date, project identification information, contract detail identification information, sales forecast identification information, and sales amount is created and registered in the storage area by the sales input unit 102i. Therefore, it is possible to clearly associate the costs and sales incurred in each work process of the project.

[0104] [4. Contribution to the United Nations Sustainable Development Goals (SDGs)] According to the present embodiment, it is possible to contribute to promoting business efficiency and appropriate management decisions of the company, and thus it is possible to contribute to Goals 8 and 9 of the SDGs.

[0105] In addition, according to the present embodiment, it is possible to contribute to reducing waste loss and promoting paperless digitization, and thus it is possible to contribute to Goals 12, 13, and 15 of the SDGs.

[0106] In addition, according to the present embodiment, it is possible to contribute to strengthening control and governance, and thus it is possible to contribute to Goal 16 of the SDGs.

[0107] [5. Other Embodiments] In addition to the embodiments described above, the present invention may be implemented in various different embodiments within the scope of the technical idea described in the claims.

[0108] For example, among the processes described in the embodiments, all or part of the processes described as being automatically performed can also be performed manually, or all or part of the processes described as being performed manually can be automatically performed by a known method.

[0109] Also, regarding the processing procedures, control procedures, specific names, information including parameters such as registered data and search conditions for each process, screen examples, and database configurations shown in this specification and the drawings, they can be arbitrarily changed unless otherwise specified.

[0110] Also, regarding the project management device 100, each illustrated component is a functional concept, and it is not necessarily physically configured as illustrated.

[0111] For example, regarding the processing functions provided by the project management device 100, particularly each processing function performed by the control unit, all or any part of them may be realized by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware by wired logic. Note that the program is recorded on a non-transitory computer-readable recording medium including programmed instructions for causing an information processing device to execute the processes described in this embodiment, and is mechanically read by the project management device 100 as needed. That is, in a storage unit such as a ROM or an HDD (Hard Disk Drive), a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded. This computer program is executed by being loaded into the RAM and constitutes the control unit in cooperation with the CPU.

[0112] In addition, this computer program may be stored in an application program server connected to the project management device 100 via an arbitrary network, and it is also possible to download all or part of it as necessary.

[0113] Also, a program for executing the processing described in this embodiment may be stored in a non-transitory computer-readable recording medium, and it can also be configured as a program product. Here, this "recording medium" includes any "portable physical medium" such as a memory card, a USB (Universal Serial Bus) memory, an SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), an EEPROM (registered trademark) (Electrically Erasable and Programmable Read Only Memory), a CD-ROM (Compact Disk Read Only Memory), an MO (Magneto-Optical disk), a DVD (Digital Versatile Disk), and a Blu-ray (registered trademark) Disc.

[0114] Also, the "program" is a data processing method described in an arbitrary language or description method, and it does not matter whether it is in the form of source code or binary code, etc. Note that the "program" is not necessarily limited to being configured singly, and also includes those that are distributed as a plurality of modules or libraries, or those that achieve their functions in cooperation with another program represented by an OS. Note that for the specific configuration and reading procedure for reading the recording medium in each device shown in the embodiment, as well as the installation procedure after reading, well-known configurations and procedures can be used.

[0115] The various databases and the like stored in the storage unit are storage means such as memory devices like RAM and ROM, fixed disk devices like hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and website provision.

[0116] Also, the project management device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which an arbitrary peripheral device is connected. Further, the project management device 100 may be realized by installing software (including programs or data, etc.) that realizes the processing described in this embodiment in the device.

[0117] Furthermore, the specific forms of distribution and integration of the devices are not limited to those illustrated, and all or part of them can be functionally or physically distributed and integrated in arbitrary units according to various additions or according to the functional load. That is, the above-described embodiments may be arbitrarily combined and implemented, or the embodiments may be selectively implemented.

Explanation of Signs

[0118] 100 Project management device 102 Control unit 102a Project registration unit 102b Contract details registration unit 102c Budget registration unit 102d Injection input unit 102e Procurement input unit 102f Settlement application unit 102g Daily report input unit 102h Cost calculation unit 102i Sales input unit 102j Project revenue and expenditure management unit 102k Master maintenance unit 102l Screen display control unit 104 Communication interface unit 106 Storage unit 106a Procurement Item Master 108 Input / Output Interface Section 112 Input Device 114 Output Device 200 Server 300 Network 400 Terminal

Claims

1. A project management device including a control unit, wherein the control unit, in response to an operation by a person in charge of the sales department, creates contract detail data including project identification information for identifying a project, contract detail identification information for identifying a contract, order receipt date, and order receipt amount created for each order unit, sales forecast data including project identification information, contract detail identification information, sales forecast identification information for identifying a sales forecast, sales forecast date, and sales forecast amount created for each sales unit, and Job data including project identification information, contract detail identification information, sales forecast identification information, and Job identification information for identifying a Job created for each unit of work process, and registers the data in a storage area; a registration means; in response to an operation by a person in charge of the work department, creates expense data including an expense identification number for identifying an expense, occurrence date, project identification information, contract detail identification information, sales forecast identification information, Job identification information, expense type, and expense amount, and registers the data in the storage area; an expense input means; in response to an operation by a person in charge of the sales department, creates sales data including a sales number, sales date, project identification information, contract detail identification information, sales forecast identification information, and sales amount, and registers the data in the storage area; a sales input means; and is characterized by comprising the above. A project management device

2. The project management device according to claim 1, wherein the expense data includes purchase data, daily report data, or settlement application data.

3. The project management device according to claim 1, wherein the Job includes a Job related to a work process of requirement definition, basic design, or development.

4. The control unit further, creates budget data including budget identification information for identifying a budget, project identification information, contract detail identification information, sales forecast identification information, budget year and month, cost elements of expenses, and budget amount, and registers the data in the storage area, and is characterized by comprising a budget input means. The project management device according to claim 1

5. The control unit further, based on the contract detail data, the sales forecast data, the budget data, the expense data, and the sales data registered in the storage area, creates and outputs an income statement including a sales forecast and actual results and a cost element forecast and actual results for each fiscal year and month in units of projects, contract details, or sales forecasts. The project management device according to claim 4 is characterized by comprising an income statement creating means.

6. A project management method executed by an information processing apparatus including a control unit, which is executed in the control unit, a registration step of creating, in response to an operation by a person in charge of the sales department, contract detail data including project identification information for identifying a project, contract detail identification information for identifying a contract, order receipt date, and order receipt amount created for each order receipt unit, sales forecast data including project identification information, contract detail identification information, sales forecast identification information for identifying a sales forecast, sales forecast date, and sales forecast amount created for each sales unit, and Job data including project identification information, contract detail identification information, sales forecast identification information, and Job identification information for identifying a Job created for each unit of a work process, and registering the data in a storage area; a cost input step of creating, in response to an operation by a person in charge of the work department, cost data including a cost identification number for identifying a cost, occurrence date, project identification information, contract detail identification information, sales forecast identification information, Job identification information, type of cost, and cost amount, and registering the data in the storage area; a sales input step of creating, in response to an operation by a person in charge of the sales department, sales data including a sales number, sales date, project identification information, contract detail identification information, sales forecast identification information, and sales amount, and registering the data in the storage area; The project management method characterized by including the above steps.

7. A project management program for causing an information processing apparatus including a control unit to execute, wherein in the control unit, a registration step of creating, in response to an operation by a person in charge of the sales department, contract detail data including project identification information for identifying a project, contract detail identification information for identifying a contract, order receipt date, and order receipt amount created for each order receipt unit, sales forecast data including project identification information, contract detail identification information, sales forecast identification information for identifying a sales forecast, sales forecast date, and sales forecast amount created for each sales unit, and Job data including project identification information, contract detail identification information, sales forecast identification information, and Job identification information for identifying a Job created for each unit of a work process, and registering the data in a storage area; a cost input step of creating, in response to an operation by a person in charge of the work department, cost data including a cost identification number for identifying a cost, occurrence date, project identification information, contract detail identification information, sales forecast identification information, Job identification information, type of cost, and cost amount, and registering the data in the storage area; A sales input process that creates sales data including a sales number, a sales date, project identification information, contract detail identification information, sales plan identification information, and a sales amount in accordance with the operations of the person in charge in the sales department and registers the data in the storage area. A project management program for executing the above.

Images