JP2008250742A - Project management program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To propose a planner of a conference in a project whether opening of the conference is commensurate with a budget or not. <P>SOLUTION: When receiving information about opening of a conference from an operator, a conference management system 10 displays reservation content edition screens 25-27 showing that opening of the conference is not allowed on a display device 10a if a sum total of unit cost evaluated from man-hours required for the conference and a cumulative result amount to the opening date of the conference exceeds a cumulative budget amount to the opening date of the conference (S215: NO, S222: YES). <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a program for managing a project.

  As is well known, a project refers to an activity performed by a plurality of workers as a team in order to achieve a certain purpose within a certain period of time as an activity different from the regular work. Since the implementation of the project is costly, when the project is organized, a budget commensurate with the cost effectiveness of the deliverable is recorded. And the smaller the budget execution performance, the lower the cost rate of the deliverables, and the higher the sales than the target can be expected. As described above, since the budget execution performance of the project greatly affects the project performance, the progress management of the budget must be properly managed together with the progress management of the project.

  Patent Document 1 discloses a technique for managing a project budget. In the invention according to Patent Document 1, an administrator who manages the progress of a project registers the number of man-hours (total work time) actually taken up to that point in the system as actual data every time a predetermined period elapses. The progress degree and the execution result of the budget are grasped based on the registered record data, and the remaining planned man-hours are corrected based on the grasped progress degree and the remaining budget. That is, in the invention according to Patent Document 1, the planned man-hour is corrected based on the man-hour actually consumed.

  By the way, many meetings (meetings) are held in the project, but these meetings naturally take man-hours. However, it is often not recognized by the workers that man-hours are spent on the conference. For this reason, the conference is planned unnecessarily or unnecessary personnel may participate in the conference. In this way, in a project, a meeting may consume man-hours wastefully, so whether or not the meeting meets the budget at the stage before deciding to hold the meeting (the stage before consuming man-hours). You have to make a good judgment.

JP 2001-014402 A

  The present invention has been made in view of the conventional circumstances as described above, and the problem is to propose to a meeting planner in a project whether or not the holding of the meeting is appropriate for the budget. There is.

  A project management program devised to solve the above-described problem is a first program that stores, in a first table, a cumulative budget amount and a cumulative actual amount for each project for a predetermined period of time. Storage means, second storage means for storing the work unit price per hour of the workers participating in each project in the second table, project identification information for identifying the project and operators participating in the conference from the operator Participant identification information, meeting date information for identifying the meeting date, and meeting time information for identifying the meeting time are received through the input device, and when the receiving means accepts each piece of information, the participant identification The work unit price per hour specified by the information is read from the second table, and the meeting specified by the meeting time information Multiply in between, the single money calculation means to calculate the single money required for each worker's meeting, and the single money calculation means to calculate the single money of each worker participating in the meeting, the meeting specified by the date information Comparing means for reading out the accumulated budget amount and the accumulated actual amount from the first table, and comparing the accumulated amount obtained by adding each worker's single money to the accumulated actual amount. And, as a result of the comparison by the comparison means, when the accumulated budget amount is less than the addition amount, it is characterized by functioning as an output means for outputting that the conference cannot be held through the output device.

  When configured in this way, when the computer receives information about the conference from the operator, the computer sums the total amount of the single money estimated from the man-hours required for the conference and the accumulated actual amount up to the date of the conference. When the cumulative budget amount up to the date of the meeting is exceeded, the operation is performed so as to output that the meeting cannot be held.

  Therefore, according to the present invention, it is possible to propose to the planner of a meeting in a project whether or not the meeting is commensurate with the budget.

  The best mode for carrying out the present invention will be described below in detail with reference to the accompanying drawings.

  FIG. 1 is a configuration diagram of a conference management system 10 according to the present embodiment.

  As shown in FIG. 1, the conference management system 10 of this embodiment is a personal computer to which a conference management function is added. Accordingly, the conference management system 10 includes a display device 10a such as a liquid crystal display, an input device 10b such as a keyboard and a mouse, and a main body to which these devices 10a and 10b are connected. The main body includes a storage unit 10c, Hardware such as a CPU [Central Processing Unit] 10d and a memory unit 10e is incorporated. The storage unit 10c is a unit that stores various programs and various data. The CPU 10d is a unit that performs processing according to a program in the storage unit 10c. The memory unit 10e is a unit in which a program read from the storage unit 10c is cached or a work area of the CPU 10d is expanded.

  In order to realize the conference management function, the conference management system 10 includes an operator information management table 11, a conference room information management table 12, a project information management table 13, a project premise management table 14, and a conference information management table in the storage unit 10c. 15 and conference management software 16 are stored.

  The worker information management table 11 is a table for managing information on workers involved in a certain project in a company that uses the conference management system 10 of the present embodiment.

  FIG. 2 is a diagram illustrating an example of the data structure of the worker information management table 11.

  As shown in FIG. 2, the worker information management table 11 has the same number of records as the workers. Each record has fields of “worker name”, “password information”, “unit price per hour”, and “participating project name”. The “worker name” field is a field in which the name of the worker is recorded. The “password information” field is a field in which password information to be collated with information presented by the worker at the time of authentication is recorded. The “unit price per hour” field is a field in which the unit price per hour of the worker is recorded. The “participating project name” field is a field in which the name of the project in which the worker participates is recorded.

  The conference management system 10 in which the unit price per hour is stored for each worker in the worker information management table 11 corresponds to the second storage unit described above.

  Moreover, the meeting room information management table 12 of FIG. 1 is a table for managing the information regarding a meeting room.

  FIG. 3 is a diagram showing an example of the data structure of the conference room information management table 12.

  As shown in FIG. 3, the conference room information management table 12 has the same number of records as conference rooms owned by a company that uses the conference management system 10 of the present embodiment. Each record has fields of “conference room name”, “conference room ID [Identification]”, “unit price per hour”, and “capacity”. The “conference room name” field is a field in which the name of the conference room is recorded. The “conference room ID” field is a field in which a conference room ID for uniquely identifying the conference room is recorded. The “unit price per hour” field is a field in which the cost per hour required for using the conference room is recorded as the unit price. The “capacity” field is a field in which the maximum number of persons that can be accommodated in the conference room is recorded.

  Further, the project information management table 13 of FIG. 1 is a table for managing information related to a project formed in a company that uses the conference management system 10 of the present embodiment.

  FIG. 4 is a diagram showing an example of the data structure of the project information management table 13.

  As shown in FIG. 4, the project information management table 13 has the same number of records as the projects assembled in the company. Each record has fields of “project name”, “total budget”, “remaining budget”, “total performance”, and “upper limit value of meeting frequency per week”. The “project name” field is a field in which the name of the project is recorded. The “total budget” field is a field in which the total budget of the project is recorded. The “budget balance” field is a field in which the balance of the budget at the midpoint of the project is recorded when the project is in progress. The “total amount” field is a field in which the total amount of actual records actually executed up to the point in the middle of the project is recorded. The “weekly meeting frequency upper limit value” field is a field in which the upper limit value of the weekly frequency of the meeting held in the project is recorded.

  Further, the project preliminary management table 14 in FIG. 1 is a table for managing information on a budget for each predetermined period of time and execution results in one project. Note that this project preliminary management table 14 is prepared for each of a plurality of projects formed by the company.

  FIG. 5 is a diagram showing an example of the data structure of the project preliminary management table 14.

  As shown in FIG. 5, the project preliminary management table 14 has the same number of records as the number of days of the implementation period set for the project. Each record has the fields of “Date”, “Meeting Budget”, “Other Budget”, “Overall Budget”, “Meeting Results / Schedule”, “Other Results / Schedule”, and “Execution Results / Schedule” Have. The “conference budget” field is a field in which the budget amount recorded for the conference when the conference is held on that date is recorded. The “other budget” field is a field in which a budget amount recorded for an element other than the conference (such as purchase of software) is recorded on the date. The “total budget” field is a field in which the cumulative amount of the conference budget and other budgets from the start date of the project implementation period to the date is recorded as the total budget amount. The “conference result / schedule” field is a field in which a cost or a cost charged for the conference is recorded as an actual amount or an actual scheduled amount when the conference is held or held on that date. In the “Other Actual / Scheduled” field, when other elements other than the meeting are performed on the date, or when they are performed, the costs or costs incurred for those elements are recorded as the actual amount or the actual planned amount. It is a field. The “Execution Performance / Schedule” field is a field in which the cumulative amount of the conference performance and other performance from the start date of the project holding period to the date is recorded.

  When a meeting or other element is held for the project, the actual amount of the meeting or other element is reflected in this project actual management table 14 by a performance reflecting means (not shown) such as a preliminary management system. It is like that. Therefore, the record of the past date in the project premise management table 14 records the history of premise, and the record of the future date records the plan of premise.

  Note that the conference management system 10 that stores the accumulated total budget amount and the accumulated execution performance amount in the project predictive management table 14 corresponds to the first storage means described above.

  The conference information management table 15 in FIG. 1 is a table for managing information related to conferences held and held in each project.

  FIG. 6 is a diagram showing an example of the data structure of the conference information management table 15.

  As shown in FIG. 6, the conference information management table 15 has the same number of records as the conferences held and held in each project. Each record includes “Conference Reservation Name”, “Conference Title”, “Project Name”, “Attendee Name”, “Date”, “Start Time”, “End Time”, “Conference Room Name” and “ Each field of “comment” is included. The “conference reservation person name” field is a field in which the name of the worker who registered the information related to the conference in the table 15 is recorded. The “conference title” field is a field in which the title of the meeting is recorded. The “project name” field is a field in which the name of the project to which the conference belongs is recorded. The “Attendee Name”, “Date”, “Start Time”, and “End Time” fields are the names of attendees of the meeting, the date of the meeting, the start time of the meeting, and the end time of the meeting. Are fields to be recorded. The “conference room name” field is a field in which the name of the conference room is recorded. The “comment” field is a field in which a comment by the reservation person regarding the conference is recorded.

  The conference management software 16 in FIG. 1 is software (a program group and a data group) for performing registration and notification of a conference schedule, registration of a conference performance, and the like. The conference management software 16 includes at least an authentication program 16a and a conference reservation program 16b. In practice, the conference management software 16 includes a program for notifying the conference schedule and a program for registering the conference performance. Is not relevant and will not be described here.

  The authentication program 16a is a program for allowing an operator who intends to use the conference management software 16 to perform an authentication procedure. Therefore, the authentication program 16a is started first when the operator instructs the start of the conference management software 16. The contents of the process executed by the CPU 10d according to the authentication program 16a will be described later with reference to FIGS.

  The conference reservation program 16b is a program for registering the conference reservation for the conference planned to be held in the conference information management table 15 of FIG. The contents of the processing executed by the CPU 10d according to the conference reservation program 16b will be described later with reference to FIGS.

  As described above, the CPU 10d of the conference management system 10 configured as described above first starts the authentication program when the input device 10b is operated by the operator and the start of the conference management software 16 is instructed as described above. 16a is read from the storage unit 10c and the authentication process is started.

  FIG. 7 is a diagram showing a flow of authentication processing.

  In the first step S101 after the start of the authentication process, the CPU 10d displays a login screen on the display device 10a.

  FIG. 8 is a diagram illustrating an example of the login screen 21.

  As shown in FIG. 8, the login screen 21 includes two text boxes 21a and 21b for inputting the worker name and the password information. The login screen 21 includes a login button 21c that is clicked after the text boxes 21a and 21b have been input, and a cancel button 21d that is clicked when giving up the authentication procedure.

  After displaying the login screen 21 as shown in FIG. 8 on the display device 10a, the CPU 10d advances the process to step S102 in FIG.

  In step S102, the CPU 10d stands by until one of the two buttons 21c and 21d in the login screen 21 is clicked. When any one of the two buttons 21c and 21d is clicked, the CPU 10d advances the process to step S103.

  In step S103, the CPU 10d determines whether or not the clicked button is the cancel button 21d. When the clicked button is the cancel button 21d, the CPU 10d ends the authentication process according to FIG. On the other hand, when the clicked button is not the cancel button 21d but the login button 21c, the CPU 10d branches the process from step S103 to step S104.

  In step S104, the CPU 10d searches the worker information management table 11 of FIG. 2 using the worker name and the password information input in the two text boxes 21a and 21b when the login button 21c is clicked as search conditions. Search for.

  In the next step S105, the CPU 10d determines whether or not a record has been detected as a result of the search in step S104. If no record is detected, the CPU 10d branches the process from step S105 to step S106.

  In step S106, the CPU 10d displays a re-login screen having substantially the same contents as the login screen 21 shown in FIG. 8 on the display device 10a, and returns the process to step S102. The re-login screen may describe that the worker name or the password information does not match.

  On the other hand, if a record is detected as a result of the search in step S104, the CPU 10d advances the process from step S105 to step S107.

  In step S107, the CPU 10d displays a main screen on the display device 10a. Although not shown, the main screen includes various menu buttons. Among these buttons, a program that states that explanation is omitted (a program for notifying the conference schedule, the conference performance record) A button for starting a program for registering, etc.) is included. Further, the buttons included in the main screen include a button for starting the conference reservation program 16b. When this button is clicked by an operator who operates the input device 10b, the CPU 10d reads the conference reservation program 16b from the storage unit 10c and starts the conference reservation process.

  9 to 12 are diagrams showing the flow of the conference reservation process.

  In the first step S201 after the start of the conference reservation process, the CPU 10d reads out the names of all the conference rooms and the number of accommodated persons from the conference room information management table 12 of FIG.

  In the next step S202, the CPU 10d reads all participating project names from the record of the logged-in worker in the worker information management table 11 of FIG.

  In the next step S203, the CPU 10d displays a conference reservation registration screen on the display device 10a.

  FIG. 13 is a diagram illustrating an example of the conference reservation registration screen 22.

  As shown in FIG. 13, the conference reservation registration screen 22 includes a display field 22a in which the name of the logged-in worker is described as the conference reservation user name. The conference reservation registration screen 22 includes a title of the conference, a project name to which the conference belongs, a name of a worker who is scheduled to attend the conference, a date and time of the conference, a conference start time, a conference end time, and a conference name. Input fields 22b to 22i for inputting the name of the conference room to be held and comments about the conference are included. Among these, the input fields 22h and 22c for inputting the conference room name and the project name are text boxes in which drop-down list boxes are displayed. These drop-down list boxes include step S202 and step S202, respectively. The conference room name, the number of persons accommodated, and the project name read in S201 are listed. In addition, the input field 22d for inputting the names of workers who will attend the conference is listed in a line with a plurality of worker names separated by punctuation marks. In addition, in the input fields 22f and 22g for inputting the start time and end time of the conference, the time can be selected in units of 30 minutes. In addition, the conference reservation registration screen 22 includes a registration button 22j that is clicked after input into the input fields 22b to 21i, and a cancel button 22k that is clicked when the conference reservation is given up. Contains.

  Immediately after the conference reservation registration screen 22 is displayed, the item (character string) is input only in the project name and conference room name input fields 22c and 22h (the state shown in FIG. 13). For the other input fields 22b, 22d to 22g, 22i, items are input by the operator after the screen 22 is displayed. FIG. 14 shows the conference reservation registration screen 22 in a state where items are input in all the input fields 22b to 22i. After displaying the conference reservation registration screen 22 as shown in FIG. 13 on the display device 10a, the CPU 10d advances the process to step S204 in FIG.

  In step S204, the CPU 10d stands by until one of the two buttons 22j and 22k in the conference reservation registration screen 22 is clicked. When any one of the two buttons 22j and 22k is clicked, the CPU 10d advances the process to step S205.

  In step S205, the CPU 10d determines whether or not the clicked button is the cancel button 22k. If the clicked button is the cancel button 22k, the CPU 10d advances the process to step S230. On the other hand, when the clicked button is not the cancel button 21d but the registration button 22j, the CPU 10d branches the process from step S205 to step S206.

  In step S206, the CPU 10d determines whether or not an item (character string) is input to all the input fields 22b to 22i of the conference reservation registration screen 22 when the registration button 22j is clicked. If no item has been input in all the input fields 22b to 22i, the CPU 10d branches the process from step S206 and returns the process to step S204. On the other hand, if the item has been input to all the input fields 22b to 22i, the CPU 10d advances the process to step S207.

  In step S207, the CPU 10d adds a new record including items input in the input fields 22b to 22i of the conference reservation registration screen 22 to the conference information management table 15 in FIG.

  Note that the CPU 10d that executes steps S201 to S207 corresponds to the reception unit described above.

  In the next step S208, the CPU 10d executes a conference performance scheduled amount calculation subroutine.

  FIG. 15 is a diagram showing a flow of a conference performance scheduled amount calculation subroutine.

  After starting the conference actual scheduled amount calculation subroutine, in the first step S301, the CPU 10d determines the conference start time and end time from the latest record (record added in step S207) in the conference information management table 15 of FIG. And the meeting time is calculated from them.

  In the next step S302, the CPU 10d reads all the names (worker names) of the conference reservation person and attendees from the latest record in the meeting information management table 15 of FIG. Thereafter, the CPU 10d executes a second processing loop L2.

  In the second processing loop L2, the CPU 10d executes the processing consisting of steps S303 and S304 one by one for all worker names read in step S302.

  In step S303, the CPU 10d reads out the work unit price per hour from the record of the processing subject worker name in the worker information management table 11 of FIG.

  In the next step S304, the CPU 10d multiplies the work unit price per hour read in step S303 by the conference time calculated in step S301, thereby executing the conference of the worker indicated by the processing target worker name. Calculate the amount of money. Thereafter, the CPU 10d ends the process for this processing target worker name in the second processing loop L2.

  When the CPU 10d finishes executing the process consisting of steps S303 and S304 for all the worker names read in step S302, the CPU 10d leaves the second process loop L2 and advances the process to step S305.

  In step S305, the CPU 10d calculates the total meeting personnel cost by adding together the singles of each worker calculated in step S304.

  In the next step S306, the CPU 10d reads out the conference room name from the latest record (record added in step S207) in the conference information management table 15 of FIG.

  In the next step S307, the CPU 10d reads the unit price per hour from the conference room name record read in step S306 in the conference room information management table 12 of FIG.

  In the next step S308, the CPU 10d calculates the conference room usage amount by multiplying the unit cost per hour read in step S307 by the conference time calculated in step S301.

  In the next step S309, the CPU 10d calculates the conference actual scheduled amount by adding the total conference personnel cost calculated in step S305 and the conference room use amount calculated in step S308.

  After that, the CPU 10d ends the conference performance scheduled amount calculation subroutine according to FIG. 15, and advances the process to step S209 in FIG.

  The CPU 10d that executes step S208 corresponds to the above-described unit calculation unit.

  In step S209, the CPU 10d substitutes the conference room usage amount calculated in step S308 for the variable X.

  In the next step S210, the CPU 10d reads the project name and date from the latest record in the conference information management table 15 in FIG.

  In the next step S211, the CPU 10d specifies the record of the date in the project preliminary management table 14 (FIG. 5) corresponding to the project name read in step S210 as a processing target record.

  In the next step S212, the CPU 10d adds the conference actual scheduled amount calculated in step S208 to the value of the “conference actual / planned” field of the processing target record.

  In the next step S213, the CPU 10d adds the value of the “execution record / plan” field of the record to be processed and a series of records earlier than that to the scheduled record amount calculated in step S208. Update by.

  In the next step S214, the CPU 10d divides the value of the “execution performance / plan” field (scheduled execution result) from the value of the “total budget” field (total budget amount) of the processing target record, thereby calculating the difference. Is calculated.

  In the next step S215, the CPU 10d determines whether or not the difference calculated in step S214 is greater than zero. That is, the CPU 10d determines whether or not it is in black. If the difference is 0 or less, the CPU 10d branches the process from step S215 to step S216.

  In step S216, the CPU 10d substitutes the difference (that is, the deficit amount) calculated in step S214 for the variable Y, and proceeds to step S225 in FIG.

  On the other hand, when the difference calculated in step S214 is larger than 0, the CPU 10d advances the process from step S215 to step S217.

  In step S217, the CPU 10d has a date that is earlier than the record to be processed and a value of the “meeting result / planned” field is not zero in the project preliminary management table 14 corresponding to the project name read in step S210. Search for.

  In the next step S218, the CPU 10d determines whether or not a record has been detected as a result of the search in step S217. If the record can be detected, the CPU 10d advances the process to step S229. On the other hand, when the record cannot be detected, the CPU 10d branches the process from step S218 and executes the first processing loop L1.

  In the first processing loop L1, as a result of the search in step S217, the CPU 10d executes the processing including steps S219 to S221 in order from the oldest to the newest date for all records detected. .

  In step S219, the CPU 10d calculates the difference by dividing the value of the “execution performance / plan” field (execution performance planned amount) from the value of the “total budget” field (total budget amount).

  In the next step S220, the CPU 10d determines whether or not the difference calculated in step S219 is 0 or less. That is, the CPU 10d determines whether or not it is in red. If the difference is greater than 0, the CPU 10d branches the process from step S220, and ends the process for this process target record in the first process loop L1. On the other hand, when the difference is 0 or less, the CPU 10d advances the process to step S221.

  In step S221, the CPU 10d temporarily stores the difference (that is, the deficit) calculated in step S214 in a predetermined area of the memory unit 10e. Thereafter, the CPU 10d ends the processing for the processing target record in the first processing loop L1.

  When the CPU 10d finishes executing the process consisting of steps S219 to S221 for all the records detected as a result of the search in step S217, the CPU 10d leaves the first process loop L1 and advances the process to step S222.

  In step S222, the CPU 10d determines whether or not the deficit amount is temporarily stored in a predetermined area of the memory unit 10e. If the deficit amount is not temporarily stored in the predetermined area of the memory unit 10e, the CPU 10d branches the process from step S222 to step S223 in FIG.

  In step S223, the CPU 10d displays a registration completion notification screen on the display device 10a.

  FIG. 16 is a diagram illustrating an example of the registration completion notification screen 23.

  As shown in FIG. 16, the registration completion notification screen 23 describes that registration of conference reservation has been completed.

  After displaying the registration completion notification screen 23 as shown in FIG. 16 on the display device 10a, the CPU 10d ends the conference reservation process according to FIGS.

  On the other hand, when the deficit amount is temporarily stored in the predetermined area of the memory unit 10e in step S222 in FIG. 11, the CPU 10d advances the process to step S224.

  In step S224, the CPU 10d substitutes the largest amount of deficit temporarily stored in the predetermined area of the memory unit 10e for the variable Y, and proceeds to step S225 in FIG.

  The CPU 10d that executes steps S209 to S224 corresponds to the above-described comparison unit.

  In step S225, the CPU 10d executes a deficit elimination measure analysis subroutine.

  FIG. 17 to FIG. 24 are diagrams showing the flow of the deficit elimination measure analysis subroutine.

  In the first step S401 after the start of the deficit elimination measure analysis subroutine, the CPU 10d switches off all the flags to be described later.

  In the next step S402, the CPU 10d determines the date within the past one week from the date of the processing target record specified in step S211 in the project preliminary management table 14 (FIG. 5) corresponding to the project name read in step S210. The number of records that include the day and the value of the “meeting result / schedule” field is not zero is counted and obtained as a weekly frequency.

  In the next step S403, the CPU 10d reads the weekly conference holding frequency upper limit value from the project name record read in step S210 in the project information management table 13 of FIG.

  In the next step S404, the CPU 10d determines whether or not the weekly frequency acquired in step S402 is less than the weekly conference holding frequency upper limit value read in step S403. If the weekly frequency is less than the weekly conference opening frequency upper limit value, the CPU 10d advances the process to step S412. On the other hand, if the weekly frequency is greater than or equal to the weekly conference holding frequency upper limit value, the CPU 10d branches the process from step S404 to step S405.

  In step S405, the CPU 10d sets the date within the past month from the date of the processing target record identified in step S211 in the project pre-management table 14 (FIG. 5) corresponding to the project name read in step S210. The number of records that are included and the value of the “conference actual / planned” field is not zero is counted and acquired as a monthly frequency.

  In the next step S406, the CPU 10d calculates the quadruple upper limit value by performing a calculation of quadrupling the weekly conference holding frequency upper limit value read in step S403.

  In the next step S407, the CPU 10d determines whether or not the monthly frequency acquired in step S405 is less than the quadruple upper limit value calculated in step S406. If the monthly frequency is less than the quadruple upper limit value, the CPU 10d advances the process to step S408 in FIG.

  In step S408, the CPU 10d temporarily stores the monthly frequency acquired in step S405 and the quadruple upper limit value calculated in step S406 in a predetermined area of the memory unit 10e.

  In the next step S409, the CPU 10d switches on the frequency warning flag. This frequency warning flag is a flag that defines whether or not to display a frequency warning on a reservation content editing screen (see step S226 in FIG. 12, see FIG. 26 to FIG. 28). When this frequency warning flag is on, the reservation content edit screen displays, for example, “A meeting can only be performed once a week, but this reservation makes it twice a week. A frequency warning sentence with a content such as “the ratio of the degree is not exceeded” is described. After switching on such a frequency warning flag, the CPU 10d advances the process to step S412 of FIG.

  On the other hand, if the monthly frequency is equal to or greater than the quadruple upper limit value in step S407, the CPU 10d branches the process from step S407 to step S410.

  In step S410, the CPU 10d temporarily stores the weekly frequency acquired in step S402 and the weekly conference holding frequency upper limit value read in step S403 in a predetermined area of the memory unit 10e.

  In step S411, the CPU 10d switches on the frequency error flag. This frequency error flag is a flag that defines whether or not to display a frequency error on a reservation content edit screen (see step S226 in FIG. 12, see FIG. 26 to FIG. 28). When the frequency error flag is on, the reservation content edit screen indicates, for example, “A meeting can only be performed once a week, but this reservation makes it twice a week”. A frequency error sentence with such contents is described. After switching on such a frequency error flag, the CPU 10d advances the process to step S412 in FIG.

  In step S412, the CPU 10d counts the number of conference reservation persons and attendee names (worker names) stored in the latest record in the conference information management table 15 in FIG. .

  In the next step S413, the CPU 10d specifies a record in the “accommodated number of people” field in which the value exceeding the number of conference participants acquired in step S412 is stored from the conference room information management table 12 of FIG. Thereafter, the CPU 10d executes a third processing loop L3.

  In the third processing loop L3, the CPU 10d executes the processing consisting of steps S414 to S419 one by one in the descending order of the number of persons for all the records specified in step S413.

  In step S414, the CPU 10d calculates the conference room usage amount by multiplying the unit price per hour of the processing target record by the conference time calculated in step S208 (step S301 in FIG. 15).

  In the next step S415, the CPU 10d substitutes the variable Z for the conference room usage amount calculated in step S414.

  In the next step S416, the CPU 10d performs an operation of variable Y−variable X + variable Z. The substitution value of the variable Y is the maximum deficit amount generated by this reservation registration (step S216 in FIG. 10 or step S224 in FIG. 11), and the substitution value of the variable X is the conference room specified in the reservation. (Step S209 in FIG. 10), and the substitution value of the variable Z is the conference room usage amount when the conference room is changed (step S415 in FIG. 19).

  In the next step S417, the CPU 10d determines whether or not the value obtained as a result of the calculation in step S416 is less than zero. If the value obtained as a result of the calculation in step S416 is 0 or more, the CPU 10d branches the process from step S417, and ends the process for this processing target record in the third processing loop L3. On the other hand, if the value obtained as a result of the calculation in step S416 is less than zero, the CPU 10d advances the process to step S418.

  In step S418, the CPU 10d temporarily stores the conference room ID of the processing target record in a predetermined area of the memory unit 10e.

  In the next step S419, the CPU 10d switches on the conference room warning flag. However, if the flag has already been turned on, the CPU 10d does nothing. This conference room warning flag is a flag that defines whether or not to display a conference room warning on a reservation content edit screen (see step S226 in FIG. 12, FIG. 26 to FIG. 28). When the conference room warning flag is on, for example, a conference room warning text having a content such as “reservation registration is possible if the conference room is changed” is described on the reservation content edit screen. It has become. After switching on such a meeting room warning flag, the CPU 10d ends the process for this processing target record in the third processing loop L3.

  The CPU 10d advances the process to step S420 in FIG. 20 after completing the process consisting of steps S414 to S419 for all the records specified in step S413.

  In step S420, the CPU 10d reads all the names of conference reservation persons and attendees (worker names) stored in the latest record (record added in step S207) in the conference information management table 15 in FIG. .

  In the next step S421, the CPU 10d reads out the work unit price per hour from all the records including any of the worker names read out in step S420 in the worker information management table 11 of FIG.

  In the next step S422, the CPU 10d adds the work unit price per hour read for each worker in step S421, and substitutes the obtained value into the variable V.

  In the next step S423, the CPU 10d substitutes 0 as an initial value for the variable t. Thereafter, the CPU 10d advances the process to step S424.

  In step S424, the CPU 10d determines whether or not the substituted value of the variable t is equal to the conference time calculated in step S208 (step S301 in FIG. 15). If the substituted value of the variable t is not equal to the conference time, the CPU 10d branches the process from step S424 to step S425.

  In step S425, the CPU 10d adds 0.5 to the substitution value of the variable t.

  In the next step S426, the CPU 10d substitutes a value obtained by subtracting the substitution value of the variable t from the conference time into the variable T.

  In the next step S427, the CPU 10d executes the operation of variable Y−variable T × variable V. Note that the substitution value of the variable Y is the maximum deficit amount generated by this reservation registration (step S216 in FIG. 10 or step S224 in FIG. 11), and the substitution value of the variable T is the conference time specified in this reservation. Is a value obtained by subtracting only the variable t (step S426 in FIG. 20), and the substitution value of the variable V is the total of the work unit cost per hour of the attendee designated in this reservation (step S422 in FIG. 20).

  In the next step S428, the CPU 10d determines whether or not the value obtained as a result of the calculation in step S427 is less than zero. If the value obtained as a result of the calculation in step S427 is 0 or more, the CPU 10d branches the process from step S428, and returns the process to step S424.

  Then, when the value obtained as a result of the calculation of step S427 becomes less than zero during the execution of the processing loop of steps S424 to S428, the CPU 10d advances the process from step S428 to step S429.

  In step S429, the CPU 10d temporarily stores the substitution value of the variable T in a predetermined area of the memory unit 10e.

  In step S430, the CPU 10d switches on the meeting time warning flag. This meeting time warning flag is a flag that defines whether or not to display a meeting time warning on a reservation content edit screen (see step S226 in FIG. 12, FIG. 26 to FIG. 28) described later. When the conference time flag is on, a conference time warning text with a content such as “reservation registration is possible if the conference time is kept below T time” is described on the reservation content edit screen, for example. It has come to be. After switching on such a meeting time warning flag, the CPU 10d advances the process to step S431 in FIG.

  Further, during execution of the processing loop of steps S424 to S428, when the substituted value of the variable t becomes equal to the conference time, the CPU 10d advances the process from step S424 to step S431 in FIG.

  In step S431, the CPU 10d generates a work table to be used in subsequent processing on the memory unit 10e.

  FIG. 25 is a diagram showing an example of the data structure of the work table 24.

  As shown in FIG. 25, each record of the work table 24 has fields of “worker name”, “rank”, “meeting fee”, and “participation flag”. The “worker name” field is a field in which the worker name is recorded. The “rank” field is a field in which a rank indicating the degree to which the worker indicated by the worker name is required for the conference related to the reservation is recorded. The “conference fee” field is a field in which a fee (personnel cost) generated when the worker indicated by the worker name attends the conference related to the reservation is recorded. The “participation flag” field is a field in which a flag that defines whether or not the worker indicated by the worker name should attend the conference related to the reservation is recorded.

  The CPU 10d generates a work table 24 as shown in FIG. 25 on the memory unit 10e. At this time, no record is recorded in the generated work table 24. After generating the work table 24 in this way, the CPU 10d advances the process to step S432.

  In step S432, the CPU 10d reads all the names of conference reservation persons and attendees (worker names) stored in the latest record in the conference information management table 15 in FIG. 6 and reads the conference title from the record. Thereafter, the CPU 10d executes a fourth processing loop L4.

  In the fourth processing loop L4, the CPU 10d executes the processing including steps S433 to S448 one by one for all the worker names read in step S432.

  In step S433, the CPU 10d reads the work unit price per hour corresponding to the processing subject worker name from the worker information management table 11 of FIG.

  In the next step S434, the CPU 10d multiplies the work unit price per hour read out in step S433 by the meeting time calculated in step S208 (step S301 in FIG. 15), so that the work indicated by the processing target worker name is performed. The person's meeting fee is calculated.

  In the next step S435, the CPU 10d reads the participating project name from the record of the processing subject worker name in the worker information management table 11 of FIG.

  In the next step S436, the CPU 10d searches for the project name included in the latest record in the conference information management table 15 in FIG. 6 from the participating project names read in step S435.

  In the next step S437, the CPU 10d determines whether or not the same project name has been detected as a result of the search in step S436. If the same project name can be detected, the CPU 10d advances the process to step S438 in FIG.

  In step S438, the CPU 10d determines whether or not the processing subject worker name matches the conference reservation person name of the latest record in the conference information management table 15 in FIG. If the processing subject worker name matches the conference reservation person name, the CPU 10d advances the process to step S441. On the other hand, if the processing target worker does not match the conference reservation person name, the CPU 10d branches the process from step S438 to step S439.

  In step S439, the CPU 10d uses the process target worker name, the project name included in the latest record in the meeting information management table 15 in FIG. 6 and the meeting title read in step S432 as search conditions, as a search condition. The information management table 15 is searched.

  In the next step S440, the CPU 10d determines whether or not five or more records are detected as a result of the search in step S439. When five or more records are detected, the CPU 10d branches the process from step S440 to step S441.

  In step S441, the CPU 10d registers, in the work table 24 of FIG. 25, a record including the name of the processing target worker, the meeting price of the worker calculated in step S434, and a rank indicating “5”. Thereafter, the CPU 10d ends the process for this processing target worker name in the fourth processing loop L4.

  On the other hand, if less than five records are detected as a result of the search in step S439, the CPU 10d advances the process from step S440 to step S442.

  In step S442, the CPU 10d determines whether or not three or more records are detected as a result of the search in step S439. If only three records have been detected, the CPU 10d branches the process from step S442 to step S443.

  In step S443, the CPU 10d registers, in the work table 24 of FIG. 25, a record including the name of the processing target worker, the meeting price of the worker calculated in step S434, and the rank indicating “3”. Thereafter, the CPU 10d ends the process for this processing target worker name in the fourth processing loop L4.

  On the other hand, as a result of the search in step S439, if three or more records are detected, the CPU 10d advances the process from step S442 to step S444.

  In step S444, the CPU 10d registers, in the work table 24 of FIG. 25, a record including the name of the processing target worker, the meeting price of the worker calculated in step S434, and the rank indicating “4”. Thereafter, the CPU 10d ends the process for this processing target worker name in the fourth processing loop L4.

  On the other hand, as a result of the search in step S436 in FIG. 21, if the same project name cannot be detected, the CPU 10d branches the process from step S437 to step S445 in FIG.

  In step S445, the CPU 10d uses the process target worker name, the project name included in the latest record in the meeting information management table 15 in FIG. 6 and the meeting title read in step S432 as search conditions to search for the meeting in FIG. The information management table 15 is searched.

  In the next step S446, the CPU 10d determines whether or not one or more records are detected as a result of the search in step S445. If one or more records are detected, the CPU 10d advances the process to step S447.

  In step S447, the CPU 10d registers, in the work table 24 of FIG. 25, a record including the name of the processing target worker, the meeting price of the worker calculated in step S434, and the rank indicating “2”. Thereafter, the CPU 10d ends the process for this processing target worker name in the fourth processing loop L4.

  On the other hand, if no record is detected as a result of the search in step S445, the CPU 10d branches the process from step S446 to step S448.

  In step S448, the CPU 10d registers in the work table 24 of FIG. 25 a record including the name of the worker to be processed, the meeting price of the worker calculated in step S434, and a rank indicating “1”. Thereafter, the CPU 10d ends the process for this processing target worker name in the fourth processing loop L4.

  When the CPU 10d finishes executing the process consisting of steps S433 to S448 for all the worker names read in step S432, the CPU 10d leaves the fourth process loop L4 and proceeds to step S449 in FIG.

  In step S449, the CPU 10d rearranges the records in the work table 24 of FIG. 25 so that the records are arranged in order from the higher rank to the lower rank.

  In the next step S450, the CPU 10d arranges the records of the same rank among the records in the work table 24 of FIG. 25 so that the conference singles are arranged in order from the largest to the smallest. Rearrange.

  In the next step S451, the CPU 10d switches on all the participation flags in the work table 24 of FIG. Thereafter, the CPU 10d executes a fifth processing loop L5.

  In the fifth processing loop L5, the CPU 10d executes the processing consisting of steps S452 to S455 one by one in descending order of rank for all the records in the work table 24 of FIG.

  In step S452, the CPU 10d switches off the participation flag of the processing target record.

  In the next step S453, the CPU 10d calculates the total amount by adding up all the meeting singles of the records whose participation flag is OFF in the work table 24 in FIG. 25, and substitutes the total amount into the variable P.

  In the next step S454, the CPU 10d executes the calculation of the variable Y-variable P. The substitution value of the variable Y is the maximum deficit amount generated by the reservation registration (step S216 in FIG. 10 or step S224 in FIG. 11), and the substitution value of the variable P is the attendee specified in the reservation. Is the total labor cost to be reduced when several persons are reduced (step S453 in FIG. 24).

  In the next step S455, the CPU 10d determines whether or not the value obtained as a result of the calculation in step S454 is 0 or more. When the value obtained as a result of the calculation in step S454 is 0 or more, the CPU 10d ends the process for this processing target record in the fifth processing loop L5. On the other hand, if the value obtained as a result of the calculation in step S454 is less than 0, the CPU 10d branches the process from step S457 to leave the fifth process loop L5 and proceeds to step S456.

  In step S456, the CPU 10d switches on the attendee warning flag. The attendee warning flag is a flag that defines whether or not to display an attendee warning on a reservation content edit screen (see step S226 in FIG. 12, FIG. 26 to FIG. 28). When the attendee warning flag is on, an attendee warning text with a content such as “Registration can be registered if two workers cancel attendance” is displayed on the reservation content edit screen, for example. To be described. After the attendant warning flag is turned on, the CPU 10d ends the deficit elimination measure analysis subroutine according to FIGS. 17 to 24, and advances the process to step S226 in FIG.

  Also, when the process consisting of steps S452 to S455 has been executed for all the records in the work table 24 in FIG. 25 without branching the process in step S455, the CPU 10d continues to execute the fifth process loop L5. The deficit solution analysis subroutine according to FIGS. 17 to 24 is terminated without executing step S456. Thereafter, the CPU 10d advances the process to step S226 in FIG.

  In step S226, the CPU 10d displays a reservation content edit screen on the display device 10a based on the states of various flags that are turned on and off by the execution of the deficit elimination measure analysis subroutine in step S225.

  FIG. 26 is a diagram showing an example of the reservation content edit screen 25 displayed when the frequency warning flag (step S409) and the conference room warning flag (step S419) are on.

  The configuration of the display field 25a and the input fields 25b to 25i of the reservation content editing screen 25 shown in FIG. 26 is the same as the display field 22a and the input fields 22b to 22i of the conference reservation registration screen 22 of FIGS. 26 differs from the conference reservation registration screen 22 in FIGS. 13 and 14 in that the warning text 25j is described in the upper part, and the registration button 22j and the cancel button 22k are in the lower part. Instead, there is a cancel button 25k and a change button 25l in the upper stage. In addition, the reservation content editing screen 25 of FIG. 26 does not function except for the input field 25h for inputting the conference room name. In the drop-down list box of the input field 25h, only the meeting room name corresponding to the meeting room ID temporarily recorded in the predetermined area of the memory unit 10e in step S418 is listed as an option. The conference room name can be selected only from these. The name of the conference room that can be selected here is such that if the conference room is selected, the budget excess in the future reservation is resolved from the actual reservation and the actual reservation (step S417; Yes). In addition, the content of the warning sentence 25j is that if the meeting room is changed, the excess budget will be resolved and the reservation will be registered, and the meeting frequency will exceed the weekly frequency limit but the monthly frequency limit will be exceeded. It includes that there is no. The contents of the warning text 25j are based on the fact that the frequency warning flag and the conference room warning flag are each turned on as described above.

  FIG. 27 is a diagram showing an example of the reservation content edit screen 26 displayed when the conference time warning flag (step S430) is on.

  The reservation content editing screen 26 shown in FIG. 27 has almost the same content as the reservation content editing screen 25 of FIG. The difference is that the content of the warning sentence 26j is different, and that the functioning input field is not the conference room name input field 26h but the start time and end time input fields 26f and 26g. As described above, the start time and end time in the input fields 26f and 26g can be selected in increments of 30 minutes. On the reservation content edit screen 26, the meeting time is selected in step S429. Selection can be made only within a range that does not exceed the substitution value of the variable T temporarily recorded in a predetermined area of the memory unit 10e. Further, the content of the warning sentence 26j includes that the conference reservation is registered if the conference time is shortened. The contents of the warning sentence 26j are based on the fact that the meeting time warning flag is on as described above.

  FIG. 28 is a diagram showing an example of the reservation content edit screen 27 displayed when the attendee warning flag (step S456) is on.

  The reservation content edit screen 27 shown in FIG. 28 has almost the same content as the reservation content edit screen 25 of FIG. The difference is that the contents of the warning text 27j are different, and the attendee name input field 27d is a table based on the work table 24 of FIG. Each row of the table in the attendee name input field 27d has an item field for inputting an operator name, a conference fee, and a check mark for designating whether or not to select as an attendee. ing. The order of the lines is the same as that of the work table 24 of FIG. A row with a check mark corresponds to a row in which the participation flag is turned on in the work table 24 of FIG. In addition, two rows that do not correspond to the work table 24 of FIG. 25 are added to this table. Of these, the second row from the bottom describes the total amount of the conference fee for the worker selected as an attendee (the worker with the check mark). Further, the bottom line of this table describes the deficit amount assigned to the variable X in step S216 in FIG. 10 or step S224 in FIG. In the table in the attendee name input field 27d, the operator can perform operations to add or remove only check marks, and cannot operate other items in the table. Yes. Further, when the check mark is added or removed, the total amount of the meeting fee of the worker selected as the attendee is increased or decreased. Further, the contents of the warning text 27j include that the conference reservation is registered if the number of attendees is reduced as appropriate. The contents of the warning text 27j are based on the fact that the attendee warning flag is on as described above.

  The CPU 10d describes a warning text that includes content corresponding to the flag that is turned on, and the reserved content editing screen 25 that is set so that only the input field corresponding to the flag that is turned on functions. 27 is displayed on the display device 10a, the process proceeds to step S227 in FIG.

  The CPU 10d that executes Step S227 corresponds to the output means described above.

  In step S227, the CPU 10d clicks the cancel button 25k (26k or 27k) or the change button 25l (26l or 27l) in the reservation content edit screen 25 (26 or 27) displayed on the display device 10a in step S226. Wait until. When any button is clicked, the CPU 10d advances the process to step S228.

  In step S228, the CPU 10d determines whether or not the clicked button is the cancel button 25k (26k or 27k). If the clicked button is not the cancel button 25k (26k or 27k) but the change button 25l (26l or 27l), the CPU 10d branches the process from step S228 to step S229.

  In step S229, the CPU 10d determines that all items input in the input fields 25b to 25i (26b to 26i or 27b to 27i) at the time when the change button 25l (26l or 27l) is clicked are displayed in FIG. The latest record in the conference information management table 15 is updated. Thereafter, the CPU 10d advances the process to step S223 in FIG.

  On the other hand, if the button clicked in step S227 is the cancel button 25k (26k or 27k), the CPU 10d advances the process from step S228 to step S230 in FIG.

  In step S230, the CPU 10d displays a registration cancellation notification screen on the display device 10a.

  FIG. 29 is a diagram illustrating an example of the registration cancellation notification screen 28.

  As shown in FIG. 29, the registration cancellation notification screen 28 describes that the registration of the conference reservation has been canceled.

  After displaying the registration cancellation notification screen 28 as shown in FIG. 29 on the display device 10a, the CPU 10d ends the conference reservation process according to FIGS.

  Since the conference management system 10 according to the present embodiment operates as described above, the operator of the system 10 activates the conference reservation program 16b and inputs each of the displayed conference reservation registration screens 22. When information related to the planned meeting is entered in the columns 22b to 22i (FIG. 14) and the registration button 22j is clicked, the registration completion notification screen 23 of FIG. 16 or the reservation content editing screen of FIGS. 25 to 27 are displayed on the display device 10a. Therefore, the operator can grasp from the registration completion notification screen 23 of FIG. 16 that the meeting is appropriate for the budget. Further, the operator can grasp that the conference cannot be held due to an excess of the budget, using the reservation content editing screens 25 to 27 shown in FIGS.

  Furthermore, in the present embodiment, when a meeting to register a reservation causes an excess of budget, if there are alternatives for the number of meetings to be held, the size of the meeting room, and the meeting time, these alternatives are This is proposed through the reservation content editing screens 25 to 27 shown in FIGS. Therefore, the operator can easily change the conference for which the reservation is to be registered, to a content appropriate for the budget.

(Appendix 1)
Computer
A first storage means for storing, in a first table, a cumulative budget amount and a cumulative actual amount for each project for a predetermined period of time for each project;
A second storage means for storing, in a second table, the unit price per hour of workers participating in each project;
From the operator, project identification information for identifying the project, participant identification information for identifying the worker participating in the conference, date information for identifying the conference date, and conference time information for identifying the conference time, Receiving means for receiving through the input device;
When the receiving means receives each piece of information, the unit price per hour of each worker specified by the participant identification information is read from the second table and multiplied by the meeting time specified by the meeting time information. , A single money calculation means for calculating the single money required for each worker's meeting,
When the unit calculation unit calculates the unit amount of each worker participating in the conference, the accumulated budget amount and the accumulated actual amount on the conference date specified by the date information are read from the first table. , A comparison means for comparing the total amount of each worker's single money to the cumulative actual amount and the cumulative budget amount,
A project management program that, as a result of comparison by the comparison means, causes a function to be output as an output means for outputting that the conference cannot be held when the accumulated budget amount is less than the added amount.

(Appendix 2)
Said computer further
As a result of the comparison by the comparison means, when the accumulated budget amount is less than the added amount, several pieces of money that can be applied to the difference between the accumulated budget amount and the added amount are identified, and the identified pieces of money The project management program according to appendix 1, wherein the identification information of each worker corresponding to 1 is functioned as absence candidate output means for outputting through the output device as identification information of absence candidates.

(Appendix 3)
Said computer further
As a result of the comparison by the comparison means, when the accumulated budget amount is less than the added amount, the ratio between the accumulated budget amount and the added amount occupies the total amount of the unit money, and the specified ratio In response, the meeting time specified by the meeting time information received by the receiving unit is shortened, and the shortened second meeting time is made to function as a change plan output unit that outputs as a change plan through the output device. The project management program according to supplementary note 1, characterized by:

(Appendix 4)
Said computer further
Third storage means for storing, in a third table, the unit price per hour and the maximum capacity of each conference room;
Function as
The accepting means accepts, through an input device, meeting room identification information for identifying a meeting room, together with the project identification information, the participant identification information, the date information, and the meeting time information, from an operator.
Said computer further
When the receiving unit receives each information, the unit price per hour of the conference room specified by the conference room identification information is read from the third table, and multiplied by the conference time specified by the conference time information, Function as usage amount calculation means for calculating the first conference room usage amount required for the conference;
The comparison means calculates the added amount by adding the total amount of each worker's single money and the conference room usage amount to the accumulated actual amount, and compares the added amount with the accumulated budget amount,
Said computer further
As a result of the comparison by the comparison means, when the accumulated budget amount is less than the additional amount, a conference room having a maximum capacity that is larger than the number of participants specified by the participant identification information is identified from the third table. The difference between the second conference room usage amount and the first conference room usage amount obtained by multiplying the unit price per hour and the conference time from the identified conference rooms is the additional amount. A conference room that exceeds the difference between the accumulated budget amount and the identified conference room identification information, functioning as conference room candidate output means for outputting through the output device as conference room candidate identification information, The project management program according to appendix 1.

(Appendix 5)
Computer
A first storage procedure for storing, for each project, a cumulative budget amount and a cumulative actual amount for each predetermined period of time in the project in a first table;
A second storage procedure for storing, in a second table, the unit price per hour of workers participating in each project;
From the operator, project identification information for identifying the project, participant identification information for identifying the worker participating in the conference, date information for identifying the conference date, and conference time information for identifying the conference time, Acceptance procedure accepted through the input device,
When each information is received in the reception procedure, the unit price per hour of each worker specified by the participant identification information is read from the second table and multiplied by the meeting time specified by the meeting time information. , A single money calculation procedure for calculating the single money required for each worker's meeting,
When the unit money of each worker participating in the conference is calculated by the unit calculation procedure, the cumulative budget amount and the cumulative actual amount of the conference date specified by the date information are read from the first table. A comparison procedure for comparing the total amount of each worker's single money to the cumulative actual amount and the cumulative budget amount; and
A project management method comprising: executing an output procedure for outputting, through an output device, that a conference is not possible when the accumulated budget amount is less than the added amount as a result of comparison in the comparison procedure.

(Appendix 6)
A first storage unit that stores, for each project, a cumulative budget amount and a cumulative actual amount for each predetermined period of time in the project in a first table;
A second storage unit for storing, in a second table, the unit price per hour of workers participating in each project;
From the operator, project identification information for identifying the project, participant identification information for identifying the worker participating in the conference, date information for identifying the conference date, and conference time information for identifying the conference time, An accepting unit that accepts an input device;
When the receiving unit receives each piece of information, the work unit price per hour of each worker specified by the participant identification information is read from the second table and multiplied by the meeting time specified by the meeting time information. , A unit for calculating the unit of money required for each worker's meeting,
When the unit calculation unit calculates the unit amount of each worker participating in the conference, the accumulated budget amount and the accumulated actual amount on the conference date specified by the date information are read from the first table. A comparison unit for comparing the total amount of each worker's single money to the cumulative actual amount and the cumulative budget amount,
A project management apparatus comprising: an output unit that outputs that a conference is impossible when the accumulated budget amount is less than the added amount as a result of comparison by the comparison unit, through an output device.

Configuration diagram of the conference management system of the present embodiment The figure which shows an example of the data structure of a worker information management table The figure which shows an example of the data structure of a meeting room information management table The figure which shows an example of the data structure of a project information management table The figure which shows an example of the data structure of a project preliminary management table The figure which shows an example of the data structure of a meeting information management table Diagram showing the flow of authentication processing Figure showing an example of the login screen Diagram showing the flow of conference reservation processing Diagram showing the flow of conference reservation processing Diagram showing the flow of conference reservation processing Diagram showing the flow of conference reservation processing The figure which shows an example of a conference reservation registration screen The figure which shows an example of a conference reservation registration screen The figure which shows the flow of the meeting actual planned amount calculation subroutine Figure showing an example of the registration completion notification screen Diagram showing the flow of the deficit resolution analysis subroutine Diagram showing the flow of the deficit resolution analysis subroutine Diagram showing the flow of the deficit resolution analysis subroutine Diagram showing the flow of the deficit resolution analysis subroutine Diagram showing the flow of the deficit resolution analysis subroutine Diagram showing the flow of the deficit resolution analysis subroutine Diagram showing the flow of the deficit resolution analysis subroutine Diagram showing the flow of the deficit resolution analysis subroutine Diagram showing an example of the data structure of a work table Diagram showing an example of the reservation details edit screen Diagram showing an example of the reservation details edit screen Diagram showing an example of the reservation details edit screen Figure showing an example of a registration cancellation notification screen

Explanation of symbols

10 conference management system 10a display device 10b input device 10c storage unit 10d CPU
10e Memory Unit 11 Worker Information Management Table 12 Conference Room Information Management Table 13 Project Information Management Table 14 Project Prediction Management Table 15 Conference Information Management Table 16 Conference Management Software 16a Authentication Program 16b Conference Reservation Program 22 Conference Reservation Registration Screen 23 Registration Completed Notification screen 25 Reserved content edit screen 25j Warning text 26 Reserved content edit screen 26j Warning text 27 Reserved content edit screen 27j Warning text 28 Registration cancellation notification screen

Claims (4)

Computer
A first storage means for storing, in a first table, a cumulative budget amount and a cumulative actual amount for each project for a predetermined period of time for each project;
A second storage means for storing, in a second table, the unit price per hour of workers participating in each project;
From the operator, project identification information for identifying the project, participant identification information for identifying the worker participating in the conference, date information for identifying the conference date, and conference time information for identifying the conference time, Receiving means for receiving through the input device;
When the receiving means receives each piece of information, the unit price per hour of each worker specified by the participant identification information is read from the second table and multiplied by the meeting time specified by the meeting time information. , A single money calculation means for calculating the single money required for each worker's meeting,
When the unit calculation unit calculates the unit amount of each worker participating in the conference, the accumulated budget amount and the accumulated actual amount on the conference date specified by the date information are read from the first table. , A comparison means for comparing the total amount of each worker's single money to the cumulative actual amount and the cumulative budget amount,
A project management program that, as a result of comparison by the comparison means, causes a function to be output as an output means for outputting that the conference cannot be held when the accumulated budget amount is less than the added amount. Said computer further
As a result of the comparison by the comparison means, when the accumulated budget amount is less than the added amount, several pieces of money that can be applied to the difference between the accumulated budget amount and the added amount are identified, and the identified pieces of money The project management program according to claim 1, wherein the identification information of each worker corresponding to 1 is functioned as absence candidate output means for outputting through the output device as identification information of absence candidates. Said computer further
As a result of the comparison by the comparison means, when the accumulated budget amount is less than the added amount, the ratio between the accumulated budget amount and the added amount occupies the total amount of the unit money, and the specified ratio In response, the meeting time specified by the meeting time information received by the receiving unit is shortened, and the shortened second meeting time is made to function as a change plan output unit that outputs as a change plan through the output device. The project management program according to claim 1, wherein: Said computer further
Third storage means for storing, in a third table, the unit price per hour and the maximum capacity of each conference room;
Function as
The accepting means accepts, through an input device, meeting room identification information for identifying a meeting room, together with the project identification information, the participant identification information, the date information, and the meeting time information, from an operator.
Said computer further
When the receiving unit receives each information, the unit price per hour of the conference room specified by the conference room identification information is read from the third table, and multiplied by the conference time specified by the conference time information, Function as usage amount calculation means for calculating the first conference room usage amount required for the conference;
The comparison means calculates the added amount by adding the total amount of each worker's single money and the conference room usage amount to the accumulated actual amount, and compares the added amount with the accumulated budget amount,
Said computer further
As a result of the comparison by the comparison means, when the accumulated budget amount is less than the additional amount, a conference room having a maximum capacity that is larger than the number of participants specified by the participant identification information is identified from the third table. The difference between the second conference room usage amount and the first conference room usage amount obtained by multiplying the unit price per hour and the conference time from the identified conference rooms is the additional amount. A conference room that exceeds the difference between the accumulated budget amount and the identified conference room identification information, functioning as conference room candidate output means for outputting through the output device as conference room candidate identification information, The project management program according to claim 1.