JP2021177427A - Project management device, project management method, and project management program - Google Patents

Abstract

To provide a project management device, a project management method, and a project management program that can manage, at an arbitrary timing, a project in which a plurality of management items may occur.SOLUTION: A project management method in a project management device includes: performing registration (maintenance) of a management item master (S210); determining whether registration of a project related to acceptance of an order is performed (S220); performing setting of management items for the registered project (S230); performing reception of forecast data (S240); determining whether there is actual result data at the acceptance of order of the project (S250); when there is the actual result data, setting an allocation flag of the actual result data to ON (S260); performing actual result data reception processing (S270); determining whether tabulation is necessary for the plurality of management items constituting the project (S280); and when the tabulation is necessary, outputting a tabulation result (S290).SELECTED DRAWING: Figure 2

Description

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

In Patent Document 1, regarding import / export business management, billing detail data is created in which billing item data, billing date data of each billing item, billing amount data, receivable amount data, reserved amount data, etc. are aggregated for each billing destination. (See paragraph [0055], step S242 of FIG. 14), and further discloses that the allocation process is performed (see claim 2, step S159 of FIG. 15).

Japanese Unexamined Patent Publication No. 2002-183267

Here, in the device as described in Patent Document 1, regarding import / export business management, accounting data can be aggregated for each billing destination, but accounting data that is not expected to be treated as accounting data yet can be collected. It cannot be counted.

By the way, in the import / export business, a series of business is generally completed after waiting for the departure or arrival of a transportation organization such as a ship. For example, in the export business using a ship, it may take several months before the ship departs, and during this time, the cargo company that arranged it changes, and the cost price fluctuates due to fluctuations in fuel prices. Or the tariffs of the export destination may change and the advance payment may fluctuate. As is clear from these examples, all accounting data will not be finalized as actual results until a series of operations in the import / export operations are completed.

And, in the device as described in Patent Document 1, unless all the accounting data is finalized, the billing amount to the billing destination as the aggregation result cannot be obtained. Therefore, within the budget, in the import / export business. There is a problem that it is not possible to grasp whether or not a series of operations is in progress before the series of operations is completed. In particular, when a series of operations is carried out for a long period of time, it has not been possible to realize by the conventional technology, although there is a request to perform the income and expenditure management or the forecast and actual management of the operations at an arbitrary timing. It should be noted that such a problem does not occur only in the import / export business, but also occurs in the situation of dealing with a project in which multiple management items can occur, and in the problem that occurs only in the balance management or the budget management. It does not occur in the project management scene as well.

The present invention has been made in view of the above-mentioned problems, and provides a project management device, a project management method, and a project management program capable of managing a project in which a plurality of management items may occur at an arbitrary timing. The purpose is to do.

In order to solve the above-mentioned problems and achieve the object, the project management device according to the present invention is a project management device provided with a control unit for managing a project in which a plurality of management items may occur. Each of the plurality of management items belongs to one of the management item related to the actual result and the management item related to the prospect, and the control unit receives the actual data for the management item related to the actual result among the plurality of management items. Receiving means, a second receiving means for receiving prospective data for the management item related to the prospect among the plurality of management items, and a tabulation means for summarizing the actual data and the prospective data to acquire aggregated data. It is characterized by having.

Further, the project management device according to the present invention further includes a display unit for displaying an image including a display screen, and the display screen is the actual data for the management items of the first group belonging to the plurality of management items. The first achievement registration screen for accepting input and the first achievement registration screen configured to accept input of prospective data for the management items of the second group different from the first group, and the above. The second achievement registration screen including a second achievement registration screen for accepting input of achievement data for the management items of the second group, and the second achievement registration means accepted via the first achievement registration screen. It is characterized in that the prospective data for the management item of the group is accepted as the actual data via the second actual result registration screen.

Further, in the project management device according to the present invention, the control unit further includes a display control unit that controls the display screen displayed on the display unit, and the display control unit via the first result registration screen. When the prospective data for the management items of the second group is received, the prospective data is displayed on the second actual result registration screen.

Further, in the project management device according to the present invention, the actual data includes at least one information of quantity, amount and unit price, and the expected data includes at least one information of quantity, amount and unit price. Moreover, the aggregation means aggregates the actual data and the expected data with respect to at least one piece of information of the quantity, amount and unit price included in the actual data and the estimated data.

Further, in the project management device according to the present invention, the project is a project related to an order, and when the control unit receives the project related to the order, the type identification information for identifying the type of the project and the project are used. It is characterized by further including a management item setting means for setting the plurality of management items based on the management item master in which the management items to be set are managed.

Further, the project management method according to the present invention is a project management method for managing a project in which a plurality of management items may occur, which is executed in an information processing apparatus provided with a control unit, and is a project management method for managing the plurality of management items. Each belongs to one of the management items related to the actual results and the management items related to the prospects, and among the plurality of management items executed by the control unit, the first reception for receiving the actual data for the management items related to the actual results. Includes a step, a second reception step of receiving prospective data for the management item related to the prospect among the plurality of management items, and a tabulation step of summarizing the actual data and the prospective data to acquire aggregated data. It is characterized by that.

Further, the project management program according to the present invention is a project management program for managing a project in which a plurality of management items may occur for execution in an information processing apparatus provided with a control unit, and the plurality of management items. Each of the above belongs to one of the management items related to the actual results and the management items related to the prospects, and among the plurality of management items to be executed by the control unit, the first one that accepts the actual data for the management items related to the actual results. A reception step of It is characterized by including.

According to the present invention, there is an effect that the forecast and actual management of a project in which a plurality of management items may occur can be performed at an arbitrary timing.

FIG. 1 is a block diagram showing an example of the configuration of a project management system including a project management device. FIG. 2 is a flowchart showing a processing procedure of the project management method executed by the project management device 100 in FIG. FIG. 3 is a flowchart showing a processing procedure of a subroutine related to the actual data reception process executed in step S270 of FIG. FIG. 4 is a diagram used to explain a plurality of management items set in step S230 of FIG. 2 and their relationships. FIG. 5 is a diagram schematically showing a construction example of a billing item master referred to when setting a plurality of management items in step S230 of FIG. FIG. 6 is a diagram schematically showing a construction example of a cost item master referred to when setting a plurality of control items in step S230 of FIG. FIG. 7 is a diagram showing a configuration example of a display screen for receiving prospective data in step S240 of FIG. FIG. 8 is a diagram schematically showing a configuration example of a billing information file for managing input information received via a display screen as shown in FIG. 7. FIG. 9 is a diagram schematically showing a configuration example of a cost information file for managing input information received via a display screen as shown in FIG. 7. FIG. 10 is a diagram schematically showing an example of a group of expected data and actual data received as a result of the determination in step S250 of FIG. FIG. 11 is a diagram showing an example of a screen configuration when a group of expected data and actual data as shown in FIG. 10 is displayed in detail. FIG. 12 is a diagram schematically showing the relationship between the billing item and the accounting screen. FIG. 13 is a diagram used to explain that the billing items are diverse. FIG. 14 is a diagram schematically showing the relationship between the cost item and the recording screen. FIG. 15 is a diagram used to explain the wide variety of cost items. FIG. 16 is a diagram schematically showing another example of the expected data input via the display screen as shown in FIG. 7, and FIG. 16 (a) shows the expected data for the billing item in FIG. b) shows the expected data for the cost item. FIG. 17 is a diagram schematically showing a case where a part of the expected data shown in FIG. 16 is accepted as actual data. FIG. 17 (a) shows a data group for a billing item, and FIG. 17 (b) shows a cost item. The data group for is shown. FIG. 18 is a diagram schematically showing an example of a file structure when the data group shown in FIG. 17 is managed by an information file. FIG. 18A is a billing information file, and FIG. 18B is a cost. Indicates an information file. FIG. 19 is a diagram schematically showing data related to the receipt input made in step S270 of FIG. 2, FIG. 19 (a) is actual data for billing items, and FIG. 19 (b) is actual data for cost items. Is shown. FIG. 20 is a diagram schematically showing a data group in which the data shown in FIG. 19 is reflected in the data group shown in FIG. 17, and FIG. 20 (a) shows a data group for a billing item in FIG. 20 (b). Shows the data group for the cost item. 21 is a diagram schematically showing an example of a file structure when the data group shown in FIG. 20 is managed by an information file. FIG. 21A is a billing information file, and FIG. 21B is a cost. Indicates an information file.

Embodiments of the present invention will be described in detail with reference to the drawings. The present invention is not limited to the present embodiment.

[1. composition]
An example of the configuration of the project management system including the project management device according to the present embodiment will be described with reference to FIG. FIG. 1 is a block diagram showing an example of the configuration of a project management system including a project management device.

The project management system 1000 shown in FIG. 1 includes a project management device 100 as an information processing device, a server 200, and a network 300 for communicably connecting the project management device 100 and the server 200.

The project management device 100 is a commercially available desktop personal computer, and is an information processing device for managing a project in which a plurality of management items may occur. One project management device 100 is installed in a department that manages a project in a business operator, such as an order receiving department. The project management device 100 is not limited to a stationary information processing device such as a desktop personal computer, but is a portable type such as a commercially available notebook personal computer, a PDA (Personal Digital Assistants), a smartphone, or a tablet personal computer. It may be an information processing device. Further, a plurality of project management devices 100 may be installed in the project management system 1000. In this case, a plurality of project management devices are provided by synchronizing between the plurality of project management devices 100. May function as the project management device 100 of.

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 part of the project management device 100 is communicably connected via an arbitrary communication path.

The communication interface unit 104 connects the project management device 100 to the network 300 so as to be communicable 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 another device via a communication line. Here, the network 300 has a function of connecting the project management device 100 and the server 200 so as to be able to communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). Therefore, the communication interface unit 104 is configured to be able to receive input information from an information processing device provided in another department, input information from an order source, and the like via the network 300 or the network 300 and the server 200. At the same time, it is configured to be able to output predetermined information to a predetermined information processing device and an ordering party.

Various databases, tables, files, and the like are stored in the storage unit 106. A computer program (including the program of the present invention) for giving a command to a CPU (Central Processing Unit) to perform various processes in cooperation with an 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) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, or the like can be used. In addition, various data used for executing the program of the present invention are stored in the storage unit 106 so that they can be written / read.

An input device 112 and an output device 114 are connected to the input / output interface unit 108. As the output device 114, a speaker or a printer can be used in addition to a monitor (including a home television). As 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.

The control unit 102 is a CPU or the like that collectively controls the project management device 100. The control unit 102 has an internal memory for storing a control program such as an OS, a program that defines various processing procedures, required data, and the like, and performs various information processing based on these stored programs. Run.

Further, the configuration of the storage unit 106 and the control unit 102 will be described in detail with reference to FIG.

As shown in FIG. 1, the storage unit 106 includes a management item master 106a, an actual data storage area 106b, a prospective data storage area 106c, and an aggregated data storage area 106d. The actual data storage area 106b and the prospective data storage area 106c may be integrated with each other.

The management item master 106a is a master that manages the type identification information that identifies the type of the project and the management items that should be set in the project. By referring to the management item master 106a, it is possible to determine the management item to be set for the project from the type identification information (for example, the project code) of the project related to the order.

The actual data storage area 106b is an area for storing actual data. The actual data is data including at least one information of quantity, amount, and unit price, and is, for example, accounting data related to accounting generated in a plurality of operations constituting the project. The prospective data storage area 106c is an area for storing prospective data. Expected data is data that includes information on at least one of quantity, amount, and unit price, and is, for example, accounting data related to accounting that can occur in a plurality of operations that make up a project.

The aggregated data storage area 106d is an area for storing aggregated data. The aggregated data is data obtained by aggregating actual data and expected data, and is processed for output as necessary. The aggregated data is created by the project management device 100 and is held in the aggregated data storage area 106d so that it can be output.

The control unit 102 includes a plurality of modules as shown in FIG. In the example shown in FIG. 1, the control unit 102 includes a management item setting unit 102a, a first reception unit 102b, a second reception unit 102c, an aggregation unit 102d, and a display control unit 102e.

When the project related to the order is received, the management item setting unit 102a manages a plurality of management items based on the management item master that manages the type identification information for identifying the project type and the management items to be set for the project. It is a module that functions as a management item setting means for setting items.

The first reception unit 102b is a module that functions as a first reception means for receiving performance data for management items related to performance among a plurality of management items. The display screen is the first achievement registration screen for accepting the input of the achievement data for the management items of the first group belonging to a plurality of management items, and for the management items of the second group different from the first group. When the first achievement registration screen configured to accept the input of prospective data and the second achievement registration screen for accepting the input of the achievement data for the management items of the second group are included, the first acceptance The unit 102b also has a function of receiving prospective data for the management items of the second group received via the first achievement registration screen as actual data via the second actual achievement registration screen. The second reception unit 102c is a module that functions as a second reception means for receiving prospective data for the management item related to the prospect among the plurality of management items.

The aggregation unit 102d is a module that functions as an aggregation means that aggregates the actual data and the expected data and acquires the aggregated data. The aggregation unit 102d is configured to aggregate the actual data and the expected data for at least one of the quantity, amount, and unit price included in the actual data and the estimated data.

The display control unit 102e is a module that functions as a display control means for controlling the display screen displayed on the display unit. When the display screen includes the first achievement registration screen and the second achievement registration screen, the display control unit 102e receives prospective data for the management items of the second group via the first achievement registration screen. In this case, it has a function of displaying the expected data on the second result registration screen.

[2. process]
Next, the project management method executed in the project management system 1000 shown in FIG. 1 will be described exemplarily.

FIG. 2 is a flowchart showing a processing procedure of a project management method executed by the project management device 100 in the project management system 1000 of FIG. In general, the process shown in FIG. 2 makes it possible to accept both the actual data for the management items related to the actual results and the prospective data for the management items related to the prospects for the project in which a plurality of management items can occur. Actual data and expected data are aggregated together and the aggregated result is output, which enables project management at any timing. Most of this process is executed by the control unit 102 of the project management device 100. In the following, as a project, regarding the management of shipping requests (shipping instructions), the case of managing the billing amount and cost in a series of operations required from cargo warehousing to shipping will be described.

In FIG. 2, first, in step S210, the project management device 100 registers (maintenance) the management item master. The management item master is a registration of a plurality of management items that may occur in the project. Here, the project means one ordering business or contracting business consisting of a series of business. An example of a project is shipping instructions in the export business. The management item is an item whose details can be managed for each billing item and / or for each cost item, and as the management item, it is possible to set an arbitrarily subdivided business of a series of business constituting the project. ..

For example, when the project is a shipping instruction (SI) in the export business, the management items include SI input (input of the project related to the order), warehousing input, warehousing input, HBL (House Bill of Lading) input, Prepaid input and billing input are set, preferably this order is set as the recommended input order, and more preferably, the management item in the order with the highest input order is set on the main screen and the management item in another order is set. Is set in the sub screen so that each of the plurality of management items belongs to one of the management item related to the actual result and the management item related to the prospect. The set input order is also reflected in the tab arrangement order and screen type when configuring the display screen. It is preferable that each control item is configured so that the billing item and the cost item corresponding to the control item can be read out. This can be achieved by preparing an item master. By associating the management item with the billing item and the cost item, it is possible to manage whether the information (numerical value) entered in the management item is the actual data related to the actual result or the expected data related to the forecast. It becomes. The management item master registration or maintenance in step S210 can be executed at any time. The case where the following steps S220 and subsequent processes are performed on the premise that the management item master has been registered will be described.

In step S220, it is determined whether or not the project related to the order is registered. Specifically, it is determined whether or not the order input screen (for example, SI input screen) of a specific project is activated. Instead of this, it may be determined whether or not the project identification information for identifying the project type has been acquired. Examples of the project identification information include an identification code unique to the shipping instruction in the export business and an identification code unique to the collection agency business in the import business.

In the following step S230, the management items of the project registered in step S220 are set. Specifically, referring to the management item master, read out the management items and billing items according to the project, and the billing items and cost items according to the management items, and if necessary, change the order of tabs on the display screen. Organize. Further, at this time, if the main screen is set, the main screen is displayed on the display screen.

Subsequently, in step S240, the prospective data is accepted. Expected data is accepted via tabs (display screens) corresponding to each management item. At the time of receiving an order, first, when the main screen is displayed, numerical values are input for the billing items and cost items expected at the time of receiving the project order. At this time, actual data (for example, advance payment or advance payment) may be input instead of expected data.

Next, in step S250, it is determined whether or not there is actual data at the time of receiving the project order. In the present embodiment, the display screen corresponding to the management item and the accounting screen that can accept the numerical values of the billing item and the cost item as the actual data are linked in advance, so that the expected data received in step S240 can be obtained. Determine if it is actual data. That is, the expected data input on the accounting screen is determined to be actual data and the expected data is accepted as actual data, while the estimated data input on the display screen other than the accounting screen is managed as the estimated data. .. It should be noted that the management item, the billing item, and the cost item need only be associated with each other, and the display screen and the accounting screen do not necessarily have to be associated with each other. For example, instead of this, when accepting the prospective data in step S240, a check box indicating that the prospective data is actual data is provided for each prospective data, and the check box is turned ON in step S250. It may be determined that there is actual data based on the results.

Then, if there is no actual data as a result of the determination in step S250 (No in step S250), the processing of steps S260 to S270 is skipped and the process proceeds to step S280. On the other hand, if there is actual data (Yes in step S250), the process proceeds to step S260, and the recording flag of the actual data is set to ON (numerical value "1"). Here, the accounting flag is a flag indicating that the numerical value is fixed (that is, there is no change) and the data has been recorded as the aggregation target when the actual data and the expected data are aggregated together. After that, the process proceeds to step S270, and the actual data reception process described in detail with reference to FIG. 3 is performed. The actual data reception process is performed to receive the information when the billing item and the cost item change after the project is ordered.

FIG. 3 is a flowchart showing a processing procedure of a subroutine related to the actual data reception process executed in step S270 of FIG.

In FIG. 3, first, in step S271, the management item is specified. Specifically, the management item is specified from the display screen activated for inputting information on the billing item or the cost item. Instead of this, the control item may be specified from the billing item or the cost item for which information has been input. Subsequently, in step S272, initial display is performed on the display screen corresponding to the management item specified in step S271. As a result of the initial display, the expected data and the actual data that have already been accepted are reflected on the display screen.

Next, in step S273, it is determined whether or not the information input via the display screen initially displayed in step S272 is registered as actual data. If it is registered as actual data (Yes in step S273), the input information is accepted as actual data, the accounting flag is set to ON in step S274, and the process proceeds to step S275. On the other hand, if it is not registered as actual data (No in step S273), step S274 is skipped (that is, the input information remains as expected data), and the process proceeds to step S275.

In step S275, it is determined whether or not information is input to the billing item or the cost item for the other management items as well. When information is input for other management items (Yes in step S275), the process returns to step S271 and the processes of steps S271 to S274 are repeated. On the other hand, when no information is input for other management items (No in step S275), the process shown in FIG. 3 is completed, the process returns to the process of FIG. 2, and the process proceeds to step S280.

Returning to FIG. 2, in step S280, it is determined whether or not aggregation is required for the plurality of management items constituting the project registered in step S220. Actually, since the aggregation is performed when the actual data and the expected data are received, it is determined whether or not it is necessary to output the aggregation result. Specifically, the determination in step S280 is performed by determining whether or not the display screen for outputting the aggregation result has been modified. Aggregation means to aggregate actual data and expected data for each aggregate item (for example, for each billing amount, for each quantity, for each unit price), and if one of the actual data and the estimated data does not exist, the other. Is aggregated only for.

If, as a result of the determination in step S280, aggregation is not necessary (No in step S280), the process returns to step S210 and waits for new registration or maintenance of the management item master, registration of other ordered projects, and the like. .. On the other hand, if aggregation is required (Yes in step S280), the process proceeds to step S290 to output the aggregation result. The output of the aggregation result may be screen display, printout, or transmission of data related to the aggregation result to the outside via the network 300. The processes of steps S280 to S290 can be executed at arbitrary timings. Then, the process of FIG. 2 is completed.

As described in detail above, according to the processing of the project management method shown in FIGS. 2 and 3, when managing a project in which a plurality of management items may occur, prospective data or information is input to the plurality of management items. When is done (Yes in steps S240 and S273), the management items related to the actual results are accepted as actual data (Yes in steps S250 and Yes in S273), while the management items related to the prospect among the plurality of management items. Is accepted as expected data (No in step S250, No in S273), and the actual data and expected data are aggregated (Yes in step S280). As a result, not only actual data but also expected data can be reflected in the aggregation result. Therefore, the user can manage the project in which a plurality of management items may occur at an arbitrary timing by outputting the aggregation result at an arbitrary timing even if all the expected data are not confirmed as the actual data. .. For example, even if the series of operations that make up the project lasts for a long period of time, the income and expenditure management or forecast / actual management of the operations can be performed at any time, and even if the forecast data changes, the aggregated results Can be easily reflected in.

Further, according to the processes of FIGS. 2 and 3, the expected data received via the first performance registration screen (step S240) is configured to be receivable as performance data via the second performance registration screen. Yes (Yes in step S273). This is a first performance registration screen for accepting input of performance data for the management items of the first group belonging to a plurality of management items, and is different from the first group in the second group. Include a first performance registration screen configured to accept input of prospective data for management items and a second performance registration screen for accepting input of performance data for management items in the second group. It can be realized by. In this way, by configuring the prospect data so that it can be accepted even on the record registration screen and making it possible to change the prospect data to the record data after the fact, the user can input the prospect data without hesitation. Not only that, you will be able to easily edit the entered prospective data even if it changes. Further, according to the processes of FIGS. 2 and 3, when the prospect data for the management items of the second group is received via the first achievement registration screen, the prospect data is initially displayed on the second achievement registration screen. It is displayed (step S272). As a result, the user can not only avoid inputting the prospective data in duplicate, but also can quickly change from the prospective data to the actual data.

Further, according to the processes of FIGS. 2 and 3, when the project is a project related to an order, when the project related to the order is accepted, the type identification information for identifying the type of the project and the management to be set for the project are managed. Based on the management item master that manages the items, a plurality of management items corresponding to a series of operations constituting the project can be set (steps S210 to S230). As a result, the time and effort required for the user to set the management item can be significantly reduced. Furthermore, it is possible to significantly suppress the occurrence of mistakes such as input omissions as compared with the case where the user sets the management items.

In the above-described embodiment, the case of totaling the amounts has been described, but the aggregation target may be at least one of the quantity, amount, and unit price included in the actual data and the expected data. In addition, when the unit prices are totaled, it is preferable to subsequently calculate the average unit price. For example, even when the same cargo is handled on two flights, the first is due to the influence of soaring fuel prices and the like. The unit price may differ between the flight and the second flight, and the cargo can be managed at the average unit price.

[3. Concrete example]
Next, specific examples of the above-described embodiment will be described with reference to FIGS. 4 to 21. In this specific example, as a project, regarding the management of shipping request (shipping instruction), the billing amount and cost in a series of operations required from cargo warehousing to shipping are managed. Hereinafter, the description will be made on the premise that the billing item master shown in FIG. 2 has been registered.

FIG. 4 is a diagram used to explain a plurality of management items set in step S230 of FIG. 2 and their relationships. The plurality of management items shown in FIG. 4 are management items corresponding to the work required for the shipping request (shipping instruction). Further, the line connecting the plurality of management items shown in FIG. 4 also shows the relationship between the display screens corresponding to the plurality of management items on the display screen. Specifically, the SI input screen is the main screen and the sub. It shows that tabs are prepared as screens according to other management items. The display screen corresponding to each management item is configured so that details (detailed information) as expected data or actual data of billing items and cost items can be accepted.

FIG. 5 is a diagram schematically showing a construction example of a billing item master referred to when setting a plurality of management items in step S230 of FIG. 2, and FIG. 6 is a diagram showing a construction example of the plurality of management items in step S230 of FIG. It is a figure which shows typically the construction example of the cost item master which is referred to at the time of setting. By preparing the billing item master and the cost item master as shown in FIGS. 5 and 6, the management items can be quickly set in step S230 of FIG. Further, as shown in FIGS. 5 and 6, by associating the billing item code and the cost item code with the accounting screen type information, it is possible to manage whether or not the display screen is the actual input screen. Further, based on the billing item code and the cost item code of the information input via each display screen, it becomes possible to quickly determine whether or not the input information is input on the accounting screen.

FIG. 7 is a diagram showing a configuration example of a display screen for receiving prospective data in step S240 of FIG. The display screen shown in FIG. 7 shows an example of the SI input screen which is the main screen of the display screens (tabs) corresponding to the plurality of management items described with reference to FIG. 4, and orders are received through this screen. Expected data of the completed project and actual data are input if necessary.

FIG. 8 is a diagram schematically showing a configuration example of a billing information file for managing input information received via a display screen as shown in FIG. 7. In the billing information file, the input information received for the billing item is managed in relation to the screen type, the order number, and the like. FIG. 9 is a diagram schematically showing a configuration example of a cost information file for managing input information received via a display screen as shown in FIG. 7. In the cost information file, the input information received for the cost item is managed in relation to the screen type, the order number, and the like.

FIG. 10 is a diagram schematically showing an example of a group of expected data and actual data received as a result of the determination in step S250 of FIG. In the example shown in FIG. 10, the data received via the SI input screen shown in FIG. 7 is shown. Each of the four records shown in FIG. 10 was received as expected data in step S240 of FIG. 2, and in the SI input screen shown in FIG. 7, the record whose accounting screen type is SI input (that is, input). When the screen and the accounting screen match), the record is accepted as actual data (Yes in step S250), and the accounting flag is set to ON (step S260).

FIG. 11 is a diagram showing an example of a screen configuration when a group of expected data and actual data as shown in FIG. 10 is displayed in detail. In FIG. 11, the record indicated by reference numeral A is actual data, and the record indicated by reference numeral B is expected data. Although not shown in FIG. 11, the actual data and the expected data are displayed so as to be distinguishable from each other. This allows the user to easily know that the prospective data exists.

FIG. 12 is a diagram schematically showing the relationship between the billing item and the accounting screen. In this specific example, the billing item or the billing item code which is the identification information thereof is associated with the accounting screen, and when the information is input to the billing item on a certain display screen, the relationship shown in FIG. 12 It is possible to quickly determine whether or not a certain screen and the accounting screen match. FIG. 13 is a diagram used to explain that the billing items are diverse. As shown in FIG. 13, when the project is a shipping instruction, various billing items are generated, and therefore, as in this specific example, it is possible for the user to input the expected data without waiting for the confirmation as the actual data. It is advantageous.

FIG. 14 is a diagram schematically showing the relationship between the cost item and the recording screen. In this specific example, the cost item or the cost item code which is the identification information thereof is associated with the accounting screen, and when the information is input to the cost item on a certain display screen, the relationship shown in FIG. 14 It is possible to quickly determine whether or not a certain screen and the accounting screen match. FIG. 15 is a diagram used to explain the wide variety of cost items. As shown in FIG. 15, when the project is a shipping instruction, various cost items are generated, and therefore, as in this specific example, it is possible for the user to input the expected data without waiting for the confirmation as the actual data. It is advantageous.

FIG. 16 is a diagram schematically showing another example of the expected data input via the display screen as shown in FIG. 7, and FIG. 16 (a) shows the expected data for the billing item in FIG. b) shows the expected data for the cost item. The data group shown in FIG. 16 is a data group input via the SI input screen which is the main screen. FIG. 17 is a diagram schematically showing a case where a part of the expected data shown in FIG. 16 is accepted as actual data. FIG. 17 (a) shows a data group for a billing item, and FIG. 17 (b) shows a cost item. The data group for is shown. The prospective data may be treated as scheduled data.

FIG. 18 is a diagram schematically showing an example of a file structure when the data group shown in FIG. 17 is managed by an information file. FIG. 18A is a billing information file, and FIG. 18B is a cost. Indicates an information file. As shown in FIG. 18, by managing the received data as an information file, it is possible to manage the match / mismatch between the input screen and the accounting screen and the ON / OFF of the accounting flag.

FIG. 19 is a diagram schematically showing data related to the receipt input made in step S270 of FIG. 2, FIG. 19 (a) is actual data for billing items, and FIG. 19 (b) is actual data for cost items. Is shown. One of the operations related to shipping instructions is the warehousing operation. In the warehousing business, for example, when a warehousing fee is received, the information is input as actual data, or existing prospective data is edited and registered as actual data (Yes in step S273). FIG. 20 is a diagram schematically showing a data group in which the data shown in FIG. 19 is reflected in the data group shown in FIG. 17, and FIG. 20 (a) shows a data group for a billing item in FIG. 20 (b). Shows the data group for the cost item. In the example shown in FIG. 20, the record relating to the warehousing fee as the expected data shown in FIG. 17 is replaced with the record relating to the warehousing fee as the actual data shown in FIG. For this replacement, the prospective data shown in FIG. 17 may be configured to be automatically deleted so that, for example, the receipt input screen only accepts records for a single receipt fee. Then, when the actual data is input, other prospective data may be deleted. 21 is a diagram schematically showing an example of a file structure when the data group shown in FIG. 20 is managed by an information file. FIG. 21A is a billing information file, and FIG. 21B is a cost. Indicates an information file. As shown in FIG. 21, when the receipt input is made, the information file shown in FIG. 18 is also updated. Similar to the warehousing input, the information file is updated when the actual data is input via the input screen that matches the accounting screen.

As described in detail above, according to this specific example, it is possible to manage the expected data and the actual data by using the information regarding the match / mismatch between the input screen and the accounting screen. Further, since the user usually uses the accounting screen when there is actual data, the user can input data without being aware of the types of actual data and expected data. This specific example has the effect of being able to provide such a user interface.

[4. Other embodiments]
In addition to the above-described embodiments, the present invention may be implemented in various different embodiments within the scope of the technical ideas described in the claims.

For example, of each of the processes described in the embodiments, all or part of the processes described as being automatically performed may be manually performed, or all of the processes described as being performed manually. Alternatively, a part thereof can be automatically performed by a known method.

In addition, the processing procedure, control procedure, specific name, information including parameters such as registration data and search conditions of each processing, screen examples, and database configuration shown in the present specification and drawings are not specified unless otherwise specified. Can be changed arbitrarily.

Further, with respect to the project management device 100 and the project management system 1000, each component shown in the figure is a functional concept and does not necessarily have to be physically configured as shown in the figure.

For example, with respect to the processing functions included in the project management device 100, particularly each processing function performed by the control unit, all or any part thereof may be realized by the CPU and a program interpreted and executed by the CPU. It may be realized as hardware by wired logic. The program is recorded on a non-temporary computer-readable recording medium including a programmed instruction for causing the information processing apparatus to execute the process described in the present embodiment, and the project management apparatus is required. Read mechanically to 100. That is, a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or an HDD (Hard Disk Drive). This computer program is executed by being loaded into the RAM, and cooperates with the CPU to form a control unit.

Further, this computer program may be stored in an application program server connected to the project management device 100 via an arbitrary network (for example, network 300), and all or a part thereof may be downloaded as needed. It is also possible to do.

Further, the program for executing the process described in the present embodiment may be stored in a non-temporary computer-readable recording medium, or may be configured as a program product. Here, the "recording medium" includes 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), and an EEPROM (registration). Trademarks) (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magnet-Optical Disk), MO (Magnet-Optical Disk), MO (Magnet-Optical Disc), DVD (Digital), DVD (Digital) It shall include any "portable physical medium". Therefore, a recording medium containing a program for executing the processing described in the present specification also constitutes the present invention.

The "program" is a data processing method described in any language or description method, regardless of the format such as source code or binary code. The "program" is not necessarily limited to a single program, but is distributed as a plurality of modules or libraries, or cooperates with a separate program represented by the OS to achieve its function. Including things. A well-known configuration or procedure can be used for a specific configuration and reading procedure for reading the recording medium in each device shown in the embodiment, an installation procedure after reading, and the like.

Various databases and the like stored in the storage unit 106 are memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and storage means such as optical disks, and are used for various processes and website provision. Stores programs, tables, databases, files for web pages, etc.

Further, 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 mounting software (including a program or data) that realizes the processing described in the present specification on the device.

Further, the specific form of distribution / integration of the device is not limited to the one shown in the drawing, and all or a part thereof may be functionally or physically in an arbitrary unit according to various additions or functional loads. It can be distributed and integrated. That is, the above-described embodiments may be arbitrarily combined and implemented, or the embodiments may be selectively implemented.

The present invention is particularly useful in managing projects where multiple control items can occur.

100 Project management device 102 Control unit 102a Management item setting unit 102b First reception unit 102c Second reception unit 102d Aggregation unit 102e Display control unit 104 Communication interface unit 106 Storage unit 106a Management item master 106b Actual data storage area 106c Expected data Storage area 106d Aggregate data storage area 108 Input / output interface unit 112 Input device 114 Output device 200 Server 300 Network 1000 Project management system

Claims (1)

A project management device equipped with a control unit for managing a project in which multiple management items may occur.
Each of the plurality of management items belongs to one of the management items related to actual results and the management items related to prospects.
The control unit
Among the plurality of management items, a first receiving means for receiving performance data for the management item related to the performance, and
A second receiving means for receiving prospective data for the management item related to the prospect among the plurality of management items, and
A project management device comprising: an aggregation means that aggregates the actual data and the prospective data and acquires the aggregated data.

Images