JP6063764B2 - Product development management program and product development management apparatus using the same - Google Patents

Description

  The present invention relates to a product development management program for managing product development and a product development management apparatus using the program.

  Conventionally, a management system for managing a product manufacturing process using an object expansion method has been proposed in Patent Document 1. In this patent document 1, the module expansion means divides a product to be produced into a plurality of semi-finished products constituting the product, and divides each semi-finished product into a plurality of components constituting the same. . In Patent Document 1, a budget is calculated for each semi-finished product and each part, and a production process is planned. By doing in this way, Patent Document 1 calculates the man-hours necessary for the production of products based on the man-hours necessary for the production of each part, and the production process of semi-finished products and parts as necessary The order can be changed to reduce man-hours.

JP 2001-318714 A

  Here, considering the application of the management system of Patent Literature 1 to the management of product development, a plurality of development themes may proceed simultaneously during product development. In the case of product development, compared to the case of product production, the management of budgets and human resources is likely to be complicated within one development theme. When the technology such as Patent Document 1 is applied to product development management as it is, integrated management of many tasks is required as the number of development themes increases, and the number of modules required for management and the scale of the database are likely to increase. .

  The present invention has been made in view of the above circumstances, a product development management program capable of easily managing a budget and human resources for each of a plurality of development themes, and product development using such a management program An object of the present invention is to provide a management apparatus.

  In order to achieve the above object, a product development management program according to the first aspect of the present invention includes a function for registering information on a plurality of newly developed products, information on specifications of the registered plurality of newly developed products, and A function for acquiring information on existing development products including information on specifications of existing development products, performance information on schedules, and performance information on man-hours, similar to each information on newly developed products including information on schedules, and the registered The registration based on the difference between the information on a plurality of newly developed products and the acquired information on each of the existing developed products and the correction information corresponding to the information on the newly developed products or the efficiency information on the development of the newly developed products The computer realizes the function of calculating and assigning the budget, human resources, and schedule of each of the newly developed products.

  The product development management device according to the second aspect of the present invention includes a product information registration unit for registering information on a plurality of newly developed products, information on specifications of the plurality of newly developed products registered, and information on schedules. Information on the specifications of the existing development product, information on the schedule, and information on the schedule and performance information on the man-hours, which are similar to each of the information on the newly developed product including The plurality of registered newly developed products based on the difference between the information and the acquired information of each of the existing developed products and the correction information corresponding to the information on the newly developed product or the efficiency information on the development of the newly developed product An allocation unit that calculates and assigns each budget, human resource, and schedule.

  According to the present invention, it is possible to provide a product development management program capable of easily managing a budget and human resources for each of a plurality of development themes, and a product development management apparatus using such a management program. .

It is a figure which shows the structure of the management apparatus of the product development which concerns on one Embodiment of this invention. It is a related figure of the information utilized between program modules. It is a flowchart which shows the management operation | movement of the newly developed product by the product development management apparatus which concerns on one Embodiment of this invention. It is a figure which shows an example of a main screen. It is a flowchart shown about a theme registration process. It is a figure which shows an example of a registration screen. It is a figure which shows the outline | summary of man-hour performance information. It is a figure which shows the detail of man-hour performance information. It is a figure which shows a man-hour graph. It is a figure which shows the example of a display of the registered information. It is a flowchart shown about an adjustment process. It is a figure which shows an example of an adjustment screen. It is a figure which shows the example of a display of a work time adjustment screen. It is an example of a display of the detailed adjustment screen of work time. It is a display example of an order time adjustment screen. It is an example of a display of the detailed adjustment screen of an order time. It is a display example of an expense time adjustment screen. It is a display example of a budget adjustment screen.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.
FIG. 1 is a diagram showing the configuration of a product development management apparatus according to an embodiment of the present invention. FIG. 2 is a related diagram of information used between program modules.

  The management apparatus 100 according to the present embodiment is, for example, a general-purpose computer apparatus. As illustrated in FIG. 1, the management apparatus 100, the module recording units 104, 106, 108, and 110, the storage unit 112, and the information recording unit A display unit 118, an input unit 116, a display unit 118, and a printing unit 120. These blocks are communicatively connected to each other via a bus 122.

  The control part 102 is comprised by CPU (Central Processing Unit), for example. The control unit 102 manages product development by linking the program modules recorded in the module recording units 104, 106, 108, and 110 with each other. The program modules recorded in these four module recording units 104, 106, 108, 110 constitute a product development management program according to the present embodiment.

  The module recording unit 104 is configured by a known recording medium such as a hard disk or a flash ROM, and is a recording medium for recording the theme management module. The theme management module is a module that manages the flow of the development process of a newly developed product in cooperation with other modules. The theme management module is a module configured to have the following four functions. That is, a theme management function, a resource allocation function, an order time management function, and a load analysis function.

  The theme management function is a function for managing theme information. The management of theme information here includes registration and update of theme information. Here, the theme information includes, for example, seven pieces of information of “product code”, “schedule”, “development scale code”, “organization code”, “function”, “rough specification”, and “new element”. The theme information is information recorded in the information recording unit 114.

  The “product code” is a code given to each newly developed product. “Schedule” is information indicating the development schedule of the newly developed product. Here, normally, development of one newly developed product is performed in a plurality of development steps. Therefore, the information on the development schedule is also divided for each development process, and includes information indicating the scheduled start date and scheduled end date of each development process, and the man-hours. “Development scale code” is a code indicating the development scale of the newly developed product. The development scale code is given by, for example, the number of man-hours (the product of the number of people and time. The unit is man-month). “Organization code” is a code indicating the name of the organization (department in charge) in charge of development of the newly developed product. An organization code is also set for each development process. “Function” is information indicating a function (role) in development of the newly developed product of the organization indicated by “organization code”. For example, when the organization is engaged in the development of a mechanical system such as a lens frame in the development department of a digital camera, information on “mechanism” is recorded as information on “function”. “Outline specification” is information indicating an outline specification required for the newly developed product. “New element” is information indicating an element to be newly installed in the newly developed product.

  The resource allocation function is a function for allocating resources (budget and human resources) required for developing a newly developed product from the man-hour performance information of the existing developed product having a similar development theme.

  The order time management function is a function for managing the order time, the order time, the delivery time, the acceptance time, and the billing time for materials required for product development.

  The load analysis function is a function for analyzing the load of the current man-hour of a newly developed product. The load here includes not only the load of human resources actually mobilized but also the load of human resources that can be mobilized from now on. The load is analyzed from the difference between the theme information and the man-hour performance information. The theme information is as described above. The man-hour record information includes “product code”, “schedule”, “organization code”, “function”, and “cost”. The “product code” in the man-hour record information corresponds to the “product code” in the theme information. The “schedule” in the man-hour record information corresponds to the “schedule” in the theme information. This is information indicating the actual start date, end date, and man-hour of each development process. The “organization code” of the man-hour record information corresponds to the “organization code” of the theme information. The “function” of the man-hour record information corresponds to the “organization” of the theme information. The “expense” in the theme performance information corresponds to the “amount” in the budget information, but this is information indicating the amount actually used.

  The module recording unit 106 is configured by a known recording medium such as a hard disk or a flash ROM, and is a recording medium for recording a human resource management module. The human resource management module is a module for managing human resource information related to product development. The human resource management module is a module configured to have the following two functions. That is, a human resource management function and a man-hour performance management function.

  The human resource management function is a function for managing personnel information and hourly unit price information. The personnel information includes, for example, four pieces of information of “personnel code”, “organization code”, “function”, and “working time”. The personnel information is information recorded in the information recording unit 114.

  The “personnel code” is a code (for example, an ID number) given to each person in the organization. The “organization code” of the personnel information is associated with the personnel code, and is a code indicating to which organization (department in charge) the personnel indicated by the personnel code belongs. “Function” is information indicating the function (role) of the organization indicated by the “organization code”. “Working time” is information indicating the scheduled work time for each time of the personnel of the personnel code. This “work time” includes work time for each “function” and work time for each person belonging to the organization corresponding to each function. Here, the “working time” may be a fixed value. In this case, it is not necessary to record “working time”.

  The hourly unit price information is information indicating the hourly unit price of each member currently registered. The market price unit information is information recorded in the information recording unit 114.

  The man-hour record management function is a function for managing the man-hour record information. The man-hour record information is package information in which man-hours (product of the number of people and the working time of each person), costs, etc. required for existing product development are summarized for each theme. The manhour performance information will be described in detail later.

  The module recording unit 108 is configured by a known recording medium such as a hard disk or a flash ROM, and is a recording medium for recording a budget management module. The budget management module is a module for managing budget information related to product development. The budget management module is a module configured to have the following three functions. That is, a budget management function, an order performance management function, and a difference analysis function.

  The budget management function is a function for managing budget information. The budget information includes, for example, six pieces of information of “budget ID”, “product code”, “account item”, “organization code”, “budget date”, and “amount”. The budget information is information recorded in the information recording unit 114.

  “Budget ID” is an ID number given to identify a budget allocated to each newly developed product under development. The “product code” corresponds to the product code of the theme information, and indicates which newly developed product is used for the budget indicated by the budget ID. The “account item” is information indicating what the budget indicated in the amount is generated. The “organization code” is a code indicating the name of the organization (department in charge) that generates the budget. “Budget date” is information indicating a date when the budget is scheduled to be generated or issued. “Amount” is information indicating a used or used cost.

  The order record management function is a function for managing order record information. The order record information corresponds to the budget information and includes, for example, six pieces of information of “budget ID”, “product code”, “account item”, “organization code”, “billing schedule”, and “amount”. Note that the order record information is information recorded in the information recording unit 114.

  “Budget ID” corresponds to the budget ID of the budget information, and when the budget indicated by the budget information is used or used, the same ID as the budget ID of the budget information is given. The “product code” is a code assigned to a newly developed product that is a target when a budget is used or used. The “account item” is information indicating what the budget indicated in the amount is for. “Organization code” is a code indicating the name of the organization that generated or generated the budget (signature in charge). “Billing schedule” is information indicating a date on which a budget is scheduled to be generated. “Amount” is information indicating the amount of the generated budget.

  The difference analysis function is a function for analyzing the difference between the budget information and the order record information, that is, how much money is actually spent on the budget in product development.

  The module recording unit 110 is configured by a known recording medium such as a hard disk or a flash ROM, and is a recording medium for recording an order management module. The order management module is a module for managing various information related to ordering of products such as ordering of actual products or prototypes, order receipt, and delivery of products or prototypes. The order management module is a module configured to have the following six functions. That is, an estimate function, an ordering function, an order receiving function, a delivery function, an acceptance function, and a billing function. The order management module is configured so that management on the ordering side and management on the order receiving side can be performed simultaneously.

  The estimate function is a function for creating an estimate prior to actually manufacturing a product or prototype in a factory or the like. The estimation function may include a function such as printing an estimate.

  The ordering function is a function for managing the ordering status of a product or prototype production to a factory. The ordering function may include a function of making an order request to the factory by e-mail, for example.

  The order receiving function is a function for managing the order receiving status of production of products or prototypes for each factory. Note that the order receiving function may include a function of making an order communication from the factory by e-mail, for example.

  The delivery function is a function for managing the delivery status of a product or a prototype. The acceptance function is a function for managing the acceptance status of the delivered product or prototype.

  The billing function is a function that manages billing from the factory that manufactured the product or prototype. The billing function may include a function such as printing a bill.

  In the above description, the module recording units 104, 106, 108, and 110 are separate recording units. However, the functions of the module recording units 104, 106, 108, and 110 may be realized by a single recording unit.

  The storage unit 112 is a storage unit used as a work memory when the control unit 102 performs management according to the modules recorded in the module recording units 104, 106, 108, and 110.

  The information recording unit 114 is composed of a known recording medium such as a hard disk, and records various types of information such as the aforementioned personnel information, man-hour record information, budget information, and order record information. Here, the information recording unit 114 may be the same recording unit as the module recording units 104, 106, 108, and 110.

  The input unit 116 is an interface such as a mouse or a keyboard for the user to perform various input operations related to the management apparatus 100. The display unit 118 displays various management screens in the management apparatus 100. The printing unit 120 prints an estimate sheet created by the management apparatus 100. The bus 122 is a transfer path for transferring data within the management apparatus 100.

  Hereinafter, the operation of the management apparatus 100 will be described. FIG. 3 is a flowchart showing the management operation of a newly developed product by the management apparatus 100. Here, the following operation of the management apparatus 100 is an example applied to product development of a digital camera, for example. The processing shown below is controlled by the control unit 102 in cooperation with each module.

  When the development management system is activated, the control unit 102 displays the main screen on the display unit 118 (step S101).

  FIG. 4 is a diagram illustrating an example of a main screen. The main screen shown in FIG. 4 displays a graph 202 indicating the development schedule of the theme that is currently in progress. This graph 202 is a graph showing a period from the scheduled start time of development to the scheduled end time of development. FIG. 4 shows a state where development of two newly developed products is proceeding simultaneously. The graph 202 allows the user to know the development schedules of a plurality of newly developed products at the same time.

  Here, when the information of many newly developed products is registered and the graph cannot be displayed on the screen, the screen is scrolled by the scroll bar to display the undisplayed graph. In the example of FIG. 4, the horizontal axis is divided into four periods: 1st quarter (1Q), 2nd quarter (2Q), 3rd quarter (3Q), and 4th quarter (4Q). There is no need to divide into four periods. For example, you may make it divide by December. Furthermore, one graph may be color-coded for each development process so that the development process for each newly developed product can be visually recognized.

  On the main screen 200, in addition to displaying the graph 202, software buttons for user operation are displayed. The main screen 200 shown in FIG. 4 shows an example in which a registration button 204a and an adjustment button 204b are displayed. The registration button 204a is a button for the user to instruct registration of information on a newly developed product. The adjustment button 204b is a button for the user to instruct the adjustment of work time allocation, budget allocation, product and prototype ordering time, etc. for each function. The user operates the pointer 206 using the input unit 116 such as a mouse, and selects the registration button 204a and the adjustment button 204b. When a button is selected, the control unit 102 executes processing according to the type of the selected button.

  In addition, a toolbar 208 and a calendar 210 may be displayed on the main screen 200 as necessary. Furthermore, by selecting various buttons displayed as the toolbar 208, it is possible to perform operations such as data storage, printing, and editing.

  After displaying the main screen, the control unit 102 determines whether or not the registration button 204a has been selected by the user (step S102). If it is determined in step S102 that the registration button 204a has been selected, the control unit 102 executes a theme registration process (step S103). Details of the theme registration process will be described later.

  When it is determined in step S102 that the registration button 204a has not been selected or after S103, the control unit 102 determines whether or not the adjustment button 204b has been selected by the user (step S104).

  If it is determined in step S104 that the adjustment button 204b has been selected, the control unit 102 executes an adjustment process (step S105). Details of the adjustment process will be described later.

  When it is determined in step S105 that the adjustment button 204b is not selected or after S105, the control unit 102 executes ordering / order management (step S106). Order / order management manages the timing of quotation, ordering, ordering, delivery, acceptance, and billing according to the development schedule information registered by the theme registration process. For example, place an order or issue an invoice when necessary.

  After the order / order management, it is determined whether or not the user has instructed to end the program of the development management system (step S107). If it is determined in step S107 that the termination of the program is not instructed, the control unit 102 returns the process to step S101. If it is determined in step S107 that the end of the program has not been instructed, the control unit 102 ends the process of FIG.

  Next, the theme registration process will be described. FIG. 5 is a flowchart showing the theme registration process. Here, the following example describes an example in which information on a new newly developed product C is registered with respect to a state where information on two newly developed products shown in FIG. 4 is registered.

  After starting the theme registration process, the control unit 102 displays a registration screen on the display unit 118 (step S201). FIG. 6 is a diagram illustrating an example of a registration screen. On the registration screen shown in FIG. 6, a graph 202 indicating the development schedule of the currently ongoing theme is displayed as in the main screen. Further, a registration form 212 for information on newly developed products is displayed on the registration screen. The user inputs five items “product name”, “theme”, “development scale”, “specification”, and “new element”. The user can input the above-mentioned five items by inputting a desired text in the input field 212a or selecting a desired item from the drop-down list 212b. The input method is not limited to these methods.

  After displaying the registration screen, the control unit 102 waits for input of information by the user (step S202). When the five items shown in FIG. 6 are input, the control unit 102 acquires man-hour record information having a theme similar to the theme inputted by the user and personnel information related to the man-hour record information (step) S203).

  FIG. 7 is a diagram showing an overview of the man-hour performance information. As shown in FIG. 7A to FIG. 7D, each man-hour performance information includes “personnel”, “man-hour”, “cost”, and “man-hour graph type” information as package information for each “theme”. It is recorded.

  “Theme” is information indicating a development theme of an existing development product. FIG. 8A shows an example of theme information in the case of developing a digital camera. As shown in FIG. 8A, the “theme” information is information of a hierarchical structure organized for each similar theme. Here, “themes” are similar, for example, the specifications are similar (the numerical value is within a predetermined range if the specification can be quantified such as the development scale), and the development concept is similar (For example, a product with the same name or a successor machine, etc.) can be considered.

  “Staff” is information indicating the number of people required to develop the product of the theme. FIG. 8B is an example of personnel information when developing a digital camera. As shown in FIG. 8B, the “personnel” information is information of a hierarchical structure organized for each function, and the number of people is recorded for each hierarchy. Note that the “function” shown in FIG. 8B is associated with the aforementioned organization code.

  “Man-hour” is the total number of man-hours required to develop the product of the theme. This man-hour is the total man-hour shown in the man-hour graph described later.

  “Cost” is the cost required to develop the product of the theme. As shown in FIG. 8C, the “cost” information is information of a hierarchical structure collected for each cost item, and the cost is recorded for each hierarchy. The name of “expense item” shown in FIG. 8C is associated with the account item described above.

  The “man-hour graph type” is information for specifying the type of the man-hour graph indicating the tendency of the man-hour load for each period of the development theme. FIG. 9 is an example of a man-hour graph. Usually, when developing a similar theme, the man-hour graph indicating the man-hour load at that time is similar. Therefore, when developing a newly developed product whose theme is similar to that of the existing developed product, the man-hour load can be predicted using the man-hour graph of the existing developed product. As a result, it is possible to adjust the development schedule so that the time when the man-hour load increases among a plurality of themes does not overlap, or to allocate a large number of personnel when the man-hour load increases.

  Here, FIG. 7 shows an example in which only the “Effect graph type” is recorded. However, as the “cost graph type”, an expense graph indicating the tendency of the cost load for each period of the development theme is shown. Information for specifying the type may be recorded.

After acquiring the man-hour record information and the personnel information, the control unit 102 determines the newly developed product registered information from the difference between the information input by the user and the man-hour record information acquired corresponding to the input information. The man-hour load is predicted (step S204). The effort load, which indicates the load of the extent of the effort to which timing has occurred, represented in the form of man-hours graph shown for example in FIG.

  Development of products with similar themes often goes through similar development processes, resulting in similar man-hours, costs, and human resources. Therefore, it is possible to predict the man-hour load of a similar newly developed product using the man-hour graph indicated by the man-hour graph type of the man-hour record information. Actually, there is a possibility that there is a difference from the man-hour record information in the development scale. The man-hour load of the newly developed product is predicted from this difference. Specifically, the existing man-hour graph or the cost graph is corrected based on the difference from the man-hour performance information. In addition, the average value of the existing man-hour graph or cost graph and the actual man-hour or cost is used as the prediction result, or a predetermined relational expression for correcting the man-hour performance information is obtained in advance, and the correction is made using it. You may do it. Further, in practice, the man-hour load may be corrected according to the specification information of the newly developed product and the information indicating the change in development efficiency at the time of development of the newly developed product. For example, if the development efficiency at the time of development is improved, the man-hour load is reduced even for similar developed products. On the other hand, if the work ability of each person decreases due to the rearrangement or replacement of human resources, the man-hour load increases even for similar developed products.

  After predicting the man-hour load, the control unit 102 searches for a period in which a development schedule for a newly developed product can be assigned (step S205). This period is a period in which the total number of man-hours for the current ongoing theme is less than or equal to a predetermined value. In the example of FIG. 4, if the development schedule of the newly developed product C is assigned in a period that does not overlap with the development schedules of both the newly developed product A and the newly developed product B, the overall man-hour load can be reduced.

  After searching for an allocatable period, the control unit 102 registers information on a newly developed product (step S206). At the time of registration, the control unit 102 registers information on “product code”, “development scale code”, “rough specification”, and “new element” in the information recording unit 114 in the “theme” input in step S202. . Further, the control unit 102 registers the start and end times of each development process in the development schedule searched in step S205 in the information recording unit 114 as “development schedule”. Further, the control unit 102 registers the “organization code” and “function” of personnel required for each development process in the information recording unit 114. Here, when there is a shortage of human resources in an organization having a function necessary for developing a newly developed product, the user is warned to that effect. The user can take measures such as recruiting missing human resources by seeing this warning.

  After registering the information, the control unit 102 displays the registered information on the display unit 118 as shown in FIG. 10, for example (step S207).

  Next, the adjustment process will be described. FIG. 11 is a flowchart showing the adjustment process.

  After starting the adjustment process, the control unit 102 displays an adjustment screen on the display unit 118 (step S301). FIG. 12 is a diagram illustrating an example of the adjustment screen. An automatic adjustment button 204c is displayed on the adjustment screen shown in FIG. The automatic adjustment button 204c is a button that is selected when the user instructs automatic processing for man-hour adjustment. Further, for example, a development schedule button 214a, a work time button 214b, an order time button 214c, a cost time button 214d, and a budget button 214e are displayed on the adjustment screen. These buttons are selected when the user manually adjusts man-hours.

  After the adjustment screen is displayed, the control unit 102 determines whether or not the development schedule button 214a has been selected (step S302). When determining in step S302 that the development schedule button 214a has not been selected, the control unit 102 shifts the process to step S303.

  If it is determined in step S302 that the development schedule button 214a has been selected, the control unit 102 performs schedule adjustment processing (step S303). In the schedule adjustment process, the control unit 102 displays a schedule adjustment screen 216 as shown in FIG. On the schedule adjustment screen 216, a schedule adjustment graph 216a similar to the graph 202 and a man-hour graph 216b corresponding to the schedule adjustment graph 216a selected by the user are displayed.

  When the schedule adjustment screen 216 shown in FIG. 12 is displayed, the user operates the input unit 116 such as a mouse to shift the schedule adjustment graph 216a (corresponding to the graph 202) to the previous or later time. For example, FIG. 12 is an example in which a schedule adjustment operation for a newly developed product C is performed. In response to this operation, the control unit 102 rewrites the contents of the “schedule” of the theme information according to the position of the schedule adjustment graph 216a after the shifting operation. Further, the control unit 102 increases or decreases the man-hour graph 216b in accordance with the change of the contents of the “schedule”. For example, as shown in FIG. 12, when the position of the schedule adjustment graph 216a is moved to a time earlier than the original time, the man-hour graph 216b also moves the man-hour graph 216b so as to move the whole to the previous time. Increase or decrease. On the other hand, when the position of the schedule adjustment graph 216a is moved to a time later than the original time, the man-hour graph 216b also increases or decreases the man-hour graph 216b so as to move the whole to the later time. In this way, the development schedule for the newly developed product C is adjusted. In this example, the start schedule of development is shifted without changing the length of the entire schedule required for the development of the newly developed product C. However, the length of the entire schedule is also changed by adjusting the start schedule. Also good.

  When the automatic adjustment button 204c is selected after the adjustment of the schedule adjustment graph 216a is performed, the control unit 102 loads the man-hour load similar to that in step S204 described above based on the information after the change of the schedule adjustment graph 216a. And assigning human resources according to the prediction result.

  Subsequently, the control unit 102 determines whether or not the work time button 214b has been selected (step S304). If it is determined in step S304 that the work time button 214b has not been selected, the control unit 102 shifts the processing to step S306.

  If it is determined in step S304 that the work time button 214b has been selected, the control unit 102 performs work time adjustment processing (step S305). In this work time adjustment process, the control unit 102 displays a work time adjustment screen 218 as shown in FIG. On the work time adjustment screen 218, a graph 202 representing the above-described development schedule and a work time adjustment graph 217a corresponding to the graph 202 selected by the user are displayed. As shown in FIG. 13, the work time adjustment graph 217a is a graph for adjusting the work time for each "function", and displays a graph for each function involved in the development of the newly developed product. Detailed adjustment buttons 218a to 218c and an overall button 218d are displayed in the vicinity of the work time adjustment corresponding to each function.

  When the work time adjustment screen 218 shown in FIG. 13 is displayed, the user performs an operation of increasing / decreasing the work time adjustment graph 217a using the input unit 116 such as a mouse. In response to this operation, the control unit 102 rewrites the content of the “work time” of the corresponding function among the “work time” of the personnel information according to the position of the work time adjustment graph after the increase / decrease operation. In this way, rough adjustment of the working time is performed.

  When any one of the function buttons 218a to 218c is selected, the control unit 102 displays a detailed adjustment screen 220 for work time shown in FIG. On the detailed adjustment screen 220, a work time adjustment graph 220a for each work scheduled to be performed by the function (organization) corresponding to the function button selected by the user is displayed. Further, an add button 222a, a delete button 222b, and a return button 222c are also displayed.

  When the detailed adjustment screen 220 shown in FIG. 14 is displayed, the user performs an operation of increasing / decreasing the work time adjustment graph 220a using the input unit 116 such as a mouse. In response to this operation, the control unit 102 rewrites the content of the “work time” of the work corresponding to the corresponding function among the “work time” of the personnel information according to the position of the work time adjustment graph 220a after the increase / decrease operation. In this way, detailed adjustment of the working time is performed.

  When the add button 222a is selected, the control unit 102 displays a work addition screen (not shown). Within this screen, the user can add a new work to the corresponding function. When a work is added, the content of “work time” of the corresponding function is rewritten. Specifically, the “work time” of the function corresponding to the added work is increased. When the delete button 222b is selected, the control unit 102 deletes the work selected by the user. When the work is deleted, the content of “work time” of the corresponding function is rewritten. Specifically, the “work time” of the function corresponding to the added work is reduced. Further, when the return button 222c is selected, a work time adjustment screen 218 shown in FIG. 13 is displayed.

  When the overall button 218d is selected, the control unit 102 adds up the work times of all functions and displays a detailed adjustment screen for the total work time.

  Further, when the automatic adjustment button 204c is selected after the adjustment of the work time adjustment graph 217a, the control unit 102 is similar to step S204 described above based on the information after the change of the work time adjustment graph 217a. Man-hour load is predicted, and human resources are allocated according to the prediction result.

  Subsequently, the control unit 102 determines whether or not the order time button 214c is selected (step S306). If it is determined in step S306 that the order time button 214c has not been selected, the control unit 102 shifts the process to step S308.

  If it is determined in step S306 that the order time button 214c has been selected, the control unit 102 performs an order time adjustment process (step S306). In this order time adjustment process, the control unit 102 displays an order time adjustment screen 224 as shown in FIG. On the order time adjustment screen 224, an order time adjustment graph 224a indicating the order time and order time of the prototype of the parts required for the development of each product and the information 224b of the parts required for the development of each product are displayed. .

  When the order time adjustment screen 224 shown in FIG. 15 is displayed, the user performs an operation of shifting the order time adjustment graph 224a to the previous or later time by using the input unit 116 such as a mouse. In response to this operation, the control unit 102 rewrites the content of “schedule” in the theme information in accordance with the position of the order time adjustment graph 224a after the shifting operation. Further, the control unit 102 is a function for managing the “budget date” of the budget information and the order record information according to the position of the order timing adjustment graph 224a after the shifting operation. Rewrite the contents of “Billing schedule” in the order record information. In this way, adjustments such as ordering time and ordering time are performed.

  Further, for example, when the portion of the information 224b is selected, the control unit 102 displays the order adjustment detail adjustment screen 226 shown in FIG. On the detailed adjustment screen 226, the ordering time, delivery time, billing time, etc. of parts necessary for development of each newly developed product are displayed in a graph. In this graph, a graph of a process that has not actually occurred yet (“billing” in the example of FIG. 16) is displayed, for example, by blinking. Further, the amount of expenses incurred or incurred at each time is displayed in a graph. The user can confirm how much cost is incurred when the drag-and-drop process is performed by dragging and dropping the graph of ordering time, delivery time, scheduled billing time, etc. to the cost graph. Is possible.

  Subsequently, the control unit 102 determines whether or not the expense time button 214d has been selected (step S308). When determining in step S308 that the expense time button 214d has not been selected, the control unit 102 shifts the processing to step S310.

  If it is determined in step S308 that the cost time button 214d has been selected, the control unit 102 performs a cost time adjustment process (step S309). In the cost time adjustment process, the control unit 102 displays a cost time adjustment screen 228 as shown in FIG. On the cost time adjustment screen 228, a cost time adjustment graph 228a indicating the ordering time and ordering time of the prototype of the parts required for the development of each product and the cost required for the development of all products are generated at any time. A graph 228b representing this is displayed. Here, in FIG. 17, a graph is displayed separately for development costs, production costs, and general management costs. This classification is an example.

  When the expense time adjustment screen 228 shown in FIG. 17 is displayed, the user performs an operation of increasing / decreasing the expense time adjustment graph 228a using the input unit 116 such as a mouse. In response to this operation, the control unit 102 has a function of managing the “budget date” of the budget information and the order record information according to the position of the cost timing adjustment graph 228a after the increase / decrease operation. Rewrite the contents of “Billing schedule” in the order record information.

  Subsequently, the control unit 102 determines whether or not the budget button 214e is selected (step S310). When determining in step S310 that the budget button 214e has not been selected, the control unit 102 shifts the processing to step S312.

  If it is determined in step S310 that the budget button 214e has been selected, the control unit 102 performs a budget adjustment process (step S311). In this budget adjustment process, the control unit 102 displays a budget adjustment screen 230 as shown in FIG. On the budget adjustment screen 230, a budget adjustment graph showing the generated budget in time series for each newly developed product is displayed. The product button 230a is also displayed. FIG. 18 shows an example in which the product button 230a related to the newly developed product A is selected. In this case, the budget adjustment screen 230 regarding the newly developed product A is displayed.

  When the budget adjustment screen 230 shown in FIG. 18 is displayed, the user performs an operation of increasing / decreasing the budget adjustment graph or dragging and dropping it on another budget adjustment graph using the input unit 116 such as a mouse. In response to these operations, the control unit 102 rewrites the contents of the “money amount” of the budget information and the order record information at the corresponding time. In this way, the budget is adjusted.

  When the product button 230a for another newly developed product is selected, the control unit 102 displays the budget adjustment screen 230 for the corresponding newly developed product.

  Subsequently, the control unit 102 determines whether or not to end the adjustment process (step S312). In step S312, for example, when the registration button 204a is selected or this development management system is terminated, it is determined that the adjustment process is terminated. If it is determined in step S <b> 312 that the adjustment process is not terminated, the control unit 102 returns the process to step 302. In step S312, when it is determined that the adjustment process is to be ended, the control unit 102 ends the process of FIG.

  As described above, according to the present embodiment, information on existing developed products is registered for each theme. By registering information for each theme, it is possible to record man-hour performance information for each theme. Complex calculations and large-scale devices are not required for predicting the man-hour load of newly developed products based on such man-hour performance information. As a result, for example, management can be performed by one PC.

  Although the present invention has been described above based on the embodiments, the present invention is not limited to the above-described embodiments, and various modifications and applications are naturally possible within the scope of the gist of the present invention. Further, in the description of each operation flowchart described above, the operation is described using “first”, “next”, and the like for convenience, but this does not mean that it is essential to perform the operations in this order. Absent.

  The display of the various screens described above is merely an example, and various changes may be made according to the theme of the newly developed product.

  A program for executing each process according to the above-described embodiment is a memory card (ROM card, RAM card, etc.), magnetic disk (floppy disk, hard disk, etc.), optical disk (CD-ROM, DVD, etc.), semiconductor memory, etc. It can be stored in a storage medium of an external storage device and distributed. Then, the control unit 102 reads the program stored in the storage medium of the external storage device, and the operation described above can be executed by controlling the operation by the read program.

  Further, the above-described embodiments include various stages of the invention, and various inventions can be extracted by appropriately combining a plurality of disclosed constituent elements. For example, even if some configuration requirements are deleted from all the configuration requirements shown in the embodiment, the above-described problem can be solved, and this configuration requirement is deleted when the above-described effects can be obtained. The configuration can also be extracted as an invention.

  DESCRIPTION OF SYMBOLS 100 ... Management apparatus, 102 ... Control part, 104, 106, 108, 110 ... Program module recording part, 112 ... Memory | storage part, 114 ... Information recording part, 116 ... Input part, 118 ... Display part, 120 ... Printing part, 122 …bus

Claims (9)

A function to register information on multiple newly developed products,
Similar to each of the newly developed product information including the information on the specifications of the plurality of newly developed products registered and information on the schedule, the existing information including the information on the specifications of the existing developed product, the performance information on the schedule, and the performance information on the man-hours. A function to obtain information on the developed product,
Based on the difference between the information on the plurality of newly developed products registered and the information on each acquired existing development product and the correction information corresponding to the information on the newly developed product or the efficiency information on the development of the newly developed product , A function of calculating and assigning each budget, human resources, and schedule of each of the plurality of newly developed products registered,
Management program for product development to make computer realize   The product development management program according to claim 1, wherein when acquiring information on the existing development product, information on the existing development product whose theme is similar to the registered new development product is acquired. The product development management program according to claim 2 , wherein at least one of information relating to specifications and information relating to schedules is similar for existing development products having similar themes.   The product development management program according to claim 1, wherein the performance information related to the man-hour is package information in which information related to expenses, human resources, and schedules required for each development process of the existing developed product is collected.   5. The product development management program according to claim 4, wherein the package information is information divided for each function of human resources. A function of analyzing the current load of human resources related to the newly developed product;
A function of adjusting the start schedule and / or the overall schedule of the newly developed product according to the load of the analyzed human resources;
A function of changing the working time for each development process of a newly developed product according to the adjusted schedule;
A function of changing the work content and work time for each human resource according to the changed work time;
6. The product development management program according to claim 1, further comprising: A function of ordering necessary materials or human resources according to the schedule or progress of development for each newly developed product;
A function of analyzing a current human resource load of the newly developed product according to the ordered material or human resource;
7. The product development management program according to claim 1, further comprising: 6. The computer further realizing a function of visually displaying information indicating a budget allocated for each development process of the newly developed product, information indicating a human resource, or information indicating a schedule on a display unit. The product development management program according to any one of the above. A product information registration section for registering information on multiple newly developed products;
Similar to each of the newly developed product information including the information on the specifications of the plurality of newly developed products registered and information on the schedule, the existing information including the information on the specifications of the existing developed product, the performance information on the schedule, and the performance information on the man-hours. Information on the developed product is acquired, the difference between the registered information on the plurality of newly developed products and the information on each of the acquired existing developed products, information on the newly developed products, or efficiency information on the development of the newly developed products An allocation unit that calculates and assigns the budget, human resources, and schedule of each of the plurality of newly developed products registered based on the correction information according to
A product development management device.