JP6232905B2 - Consignment management system and program. - Google Patents

Description

  The present invention relates to a commissioned business management system and program.

  Conventionally, when a company or the like has outsourced work, and another company has outsourced work, a consignment work management system including a user device such as a computer is introduced to manage the progress of the work and the person in charge. Sometimes. When a change occurs in a part or all of a business, the commissioned business management system may reorganize the business progress schedule, reselect a person in charge, or the like to manage the business change correctly.

Patent Document 1 below calculates the increase or decrease in the total number of man-hours and scales associated with business changes, additions, deletions, etc., for the purpose of outputting information that can easily grasp priorities in business system optimization. The business system change support system to be output is described.
JP 2012-203702 A

  By the way, when a series of tasks are outsourced and there is a change request for a task to be executed first, even if the completion of the task change is correctly reflected on the task management system, Before implementation, it is unclear whether the business changes that should be implemented first have been completed.

  Therefore, there is a problem that there is a risk of overlooking that the execution of the subsequent work is completed before the work related to the change request is completed.

  Therefore, an object of the present invention is to provide a consignment work management system capable of confirming that execution of a subsequent work is completed after the completion of the work related to the work change request.

  In order to solve the above-mentioned problem, the consignment work management system according to claim 1 is a consignment work management system including a first user device and a second user device, wherein the first user device includes: Business transmission means for transmitting a series of commissioned work to the second user device, and business change request sending means for sending a change request for part or all of the series of commissioned work to the second user device And the second user device stores the work receiving means for receiving the series of commissioned work, the work change request receiving means for receiving the change request for the work, and the executed work together with the time of execution. Business history storage means, business change history storage means for storing business change contents together with business changes, business change contents stored in the business change history storage means, and changes in the business Associating the stored operational in the operational history storage means corresponding to, and comprising: a business associate means.

  According to a second aspect of the present invention, the second user device may change a task performed in response to the task change request based on the series of commissioned tasks received by the task receiving unit. 2. The commissioned work according to claim 1, further comprising: a work detecting means for detecting a work other than the work concerned; and a man-hour calculating means for calculating the work man-hour of the work performed in response to the change request for the work. It is a management system.

  According to a third aspect of the present invention, the work history storage means stores the executed work together with a person who has executed the work, and the second user device stores the work history in the work history storage means. 3. The system according to claim 2, further comprising: a business person detection unit that detects a person who performs a business performed in response to the business change request based on the business performed and a person who performed the business. It is the commissioned business management system described.

  According to a fourth aspect of the present invention, when the second user device receives a business change request by the business change request receiving unit, the business detected by the business detection unit and the man-hour calculation 4. The entrustment according to claim 3, further comprising business schedule transmission means for transmitting the man-hour calculated by the means and the person detected by the business practitioner detection means to the first user device. It is a business management system.

  Further, in the invention according to claim 5, the work detection means detects a work based on a work stored within a certain period of work stored in the work history storage means, and detects the performer. Based on the work stored in the work history storage means and the person who performed the work, the means stored in a certain period of time and the person who performed the work are executed in accordance with the change request for the work. 5. The commissioned business management system according to claim 4, wherein a person who performs the business to be performed is detected.

  Further, in the invention described in claim 6, the business change request transmitting unit transmits a business executed in accordance with the change of the business, and the business change request receiving unit is executed in accordance with the change request of the business. The commissioned business management system according to any one of claims 2 to 5, wherein the business is received.

  The invention according to claim 7 stores the computer together with the time when the work is received, the work receiving means for receiving a series of commissioned work, the work change request receiving means for receiving a work change request, and the executed work. Work history storage means, work change history storage means for storing work change contents when the work is changed, work change contents stored in the work change history storage means, and changes to the work A program that functions as a business association unit that associates a business stored in the business history storage unit.

  According to the first and seventh aspects of the invention, it is possible to obtain a business management system capable of confirming that a subsequent business has been performed after the completion of the business related to the business change request.

  According to the second aspect of the present invention, the range and scale affected by the business change are calculated.

  According to the third aspect of the present invention, a person who performs a business performed in accordance with the business change is detected.

  According to the invention described in claim 4, the schedule of the business to be executed upon receiving the business change request is transmitted.

  According to the invention described in claim 5, based on the work carried out within a certain period, the work carried out along with the work change is detected, and the work stored within the certain period and the person who carried out the work On the basis of the above, a person who performs the business performed in accordance with the business change is detected.

  According to the invention described in claim 6, the work performed in accordance with the work change is transmitted together.

It is the schematic which shows the structure of a consignment work management system. It is a block diagram which shows the structure of a server. It is a figure which shows the content of the memory | storage part of a server. It is a figure which shows the menu screen which performs consignment work management. It is a figure which shows a business request screen. It is a figure which shows a work history screen. It is a figure which shows a change request screen. It is a figure which shows the inquiry result screen of a change request. It is a flowchart which shows the process of a change request. It is a figure which shows the content of an incidental work memory | storage part. It is a figure which shows the content of the work man-hour memory | storage part. It is a flowchart which shows the update process of work history and change history. It is a figure which shows a change log | history screen. It is a figure which shows the work history screen updated.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  FIG. 1 is a schematic diagram showing a configuration of a commissioned business management system 1 according to an embodiment of the present invention. The commissioned business management system 1 includes a client 2, a communication network 3, and a server 4. Here, the communication network 3 is, for example, the Internet, but is not necessarily an open communication network, and may be in any form as long as the client and the server can communicate with each other. .

  Further, in the present embodiment, the client 2 represents a computer possessed by a company entrusting business, and the server 4 represents a computer possessed by a company entrusted with the business. Alternatively, the client 2 may be in a department such as a company, and the server 4 may be in a different department such as the same company.

  FIG. 2 is a block diagram showing the configuration of the server 4. The server 4 includes a network connection unit 41, a storage unit 42, a control unit 43, an input unit 44, and a display unit 45. The server 4 functions as a computer by integrating at least the storage unit 42, the control unit 43, the input unit 44, and the display unit 45.

  The network connection unit 41 is composed of, for example, a network card. The network connection unit 41 is connected to the communication network 3 and communicates with the client 2 according to a predetermined communication method.

  The storage unit 42 includes, for example, a RAM (Random Access Memory) and a ROM (Read Only Memory), and stores a program executed by the control unit 43 and also functions as a work memory of the control unit 43. In the present embodiment, the storage unit 42 includes a business history storage unit 421 and the like, and is referred to when executing the program. Note that the program executed by the control unit 43 stored in the storage unit 42 may be provided via an electric communication line or stored in a computer-readable information storage medium such as a semiconductor storage element. And may be provided.

  The control unit 43 includes, for example, a CPU (Central Processing Unit), and controls the entire server 4 by executing a program stored in the storage unit 42. For example, the control unit 43 controls communication with the client 2 using the network connection unit 41.

  The input unit 44 is, for example, a pointing device such as a mouse or a keyboard, and outputs a user instruction to the control unit 40.

  The display unit 45 is, for example, a liquid crystal display device, and displays information related to the commissioned business management system 1.

  Although FIG. 2 shows the configuration of the server 4, the client 2 also has the same configuration. However, the contents of the storage units of the client 2 and the server 4 are not necessarily the same.

  FIG. 3 is a diagram illustrating the contents of the storage unit 42 of the server 4. The storage unit 42 includes a business history storage unit 421, a change history storage unit 422, an incidental business storage unit 423, and a business man-hour storage unit 424. The stored contents will be described sequentially in the process of explaining the operation of the commissioned business management system.

  FIG. 4 is a diagram showing a menu screen 5 related to consignment work management displayed on the client 2. The menu screen 5 includes a business request button 51, a change request button 52, a business history button 53, a change history button 54, and a mouse pointer 55. When each button is clicked with the mouse pointer 55, the screen changes to a screen that handles the function indicated by the button.

  The menu screen 5 and each screen shown below are displayed on an Internet browser activated by the client 2 based on, for example, a command written in HTML (HyperText Markup Language) stored in the storage unit 42 of the server 4. Shall be. In addition, the server 4 can display the same.

  Before displaying the menu screen 5 on the client 2, an authentication screen may be displayed in order to authenticate that the person who operates the client 2 is authorized to handle the commissioned work. In this case, the storage unit 42 of the server 4 stores authentication information of an authorized person and collates the authentication information on the authentication screen.

  FIG. 5 is a diagram showing a business request screen 6 displayed when the business request button 51 is clicked on the menu screen 5. The business request screen 6 includes a requested business confirmation column 61, a request button 62, a cancel button 63, a business input column 64, an add button 65, and a mouse pointer 66.

  In the “task” column of the requested task confirmation column 61, “A” and “B”, which are the names of the commissioned tasks to be requested, are shown, and in the “Attached Task” column, the task A includes an accompanying task “a1”. , A2 ”and that the business B does not have any supplementary business. Here, the incidental work is a series of work carried out in accordance with the execution of the work A, and refers to a work that cannot be executed unless the execution of the work A is completed. However, the incidental tasks a1 and a2 are independent, and either one may be performed first. For example, when the incidental operation a1 is performed, it cannot be performed prior to the operation A, but can be performed prior to the incidental operation a2.

  In the present embodiment, it is assumed that there is only one task that must be completed before a certain task is performed. In other words, there will be no incidental work that cannot be undertaken without completing multiple work. If we consider the case where there are a maximum of N tasks (N is a positive integer) that must be completed prior to carrying out a certain task, we will remove this restriction. Considering “Attached Business 2”-“Attached Business N”, “Attached Business n” may be implemented only after “Attached Business (n−1)” is completed (n is an integer from 1 to N) And “Attached business 0” means “business”).

  The business consignor operating the client 2 confirms the items described in the requested business confirmation column 61, and if there is no mistake in the content of the request, clicks the request button 62, and performs a series of commissioned business to the server 4. Send. Here, if there is an error in the contents of the request, the user can click the cancel button 63 to change to the menu screen 5. It should be noted that the content of the request shown in the request work confirmation column 61 may be edited as appropriate or partly deleted.

  The business input column 64 is a column for inputting a series of commissioned business to be requested. The fields “Business” and “Attached Business” are required to be entered. If there is no supplementary business, the No. displayed in the Requested Business Confirmation column 61 is displayed. As in column 2, enter that there is no incidental work. After the input, by clicking the add button 65, the input content is added to the requested task confirmation column 61. The business input column 64 may include a column for designating a delivery date of a business and a person in charge.

  FIG. 6 is a diagram showing a business history screen 7 displayed when the business history button 53 is clicked on the menu screen 5. The business history screen 7 includes a business history display field 71, a return button 72, and a mouse pointer 73.

  In the business history display column 71, the business history stored in the business history storage unit 421 is displayed. Here, each row includes a “request date” column, a “business completion date” column, a “business” column, a “person in charge” column, and a “related change history” column. Since none of the business histories shown in FIG. 6 has a related change history, the “related change history” column is blank.

  In the present embodiment, it is assumed that the business shown in the requested business confirmation column 61 in FIG. 5 is requested on April 1, 2013. The business C and the supplementary business c1 are business not shown in FIG. 5 and are business requested on June 4, 2013. In the business history display column 71 of FIG. From the description of 1, it can be read that the execution of the operation A was completed on April 10, 2013 and the person in charge was the former. Hereinafter, no. 2-No. The same applies to 6.

  Comparing the business completion dates of business A and a1, it can be seen that the subsequent a1 is completed after the completion of business A. The same applies to a2, and the same can be read for operations C and c1.

  When browsing the business history is completed, the return button 72 is clicked to return to the menu screen 5.

  FIG. 7 is a diagram showing a change request screen 8 displayed when the change request button 52 is clicked on the menu screen 5. The change request screen 8 includes a change content confirmation column 81, an incidental task search range specification column 82, a person-in-charge search range specification column 83, an inquiry button 84, a cancel button 85, a change input column 86, an add button 87, and a mouse pointer 88. .

  In the “work” column of the change content confirmation column 81, “A”, which is the name of the business that is about to be requested for change, is indicated, the “accompanying business” field is blank, and the “reason for change” field is “specification”. The reason is “for change” and a “display” button is shown in the “detailed contents” column. Here, by clicking the display button, a detailed description of what change should be made is shown.

  The business change request is made after inquiring of the server 4 about the business related to the change request and confirming the result. At the time of inquiry, information stored in the storage unit 42 of the server 4 regarding matters such as whether there is no incidental work, who is the appropriate person in charge, and how much work is being carried out when the work is changed It will be determined based on. Processing performed at the time of inquiry will be described later.

  The incidental work search range designation column 82 is used to specify the period from the point of inquiry to which search object to be searched for whether there is an incidental work in the work related to the change request when making a change request inquiry. In the example shown in FIG. 7, a search for incidental work is performed based on the work requested one year before the inquiry time.

  The person-in-charge search range designation field 83 includes the search target to be searched for whether there is a person who has been in charge of the work performed in accordance with the change request in the past when the change request is inquired. It is what you specify. In the example shown in FIG. 7, the person in charge is searched based on the work requested one year before the inquiry and the person in charge of the work.

  The business consignor operating the client 2 confirms the items described in the change content confirmation column 81, and if there is no mistake, clicks the inquiry button 84 to inquire the server 4 about the content of the change request. If no change request is made, the user can click the cancel button 85 to return to the menu screen 5.

  The change input field 86 is a field for inputting a business to be requested for change. Enter the name of the business to be changed in the “business” column, and enter the incidental business of the business related to the change in the “incidental business” column. Here, the input to the incidental work column is arbitrary, and the incidental work is searched and presented when making an inquiry to the server 4 without input. Although the input to the “reason for change” column is optional, the “detailed content” column is an indispensable input item because it is necessary to tell what change should be made. In addition, the business consignor may be able to specify the delivery date and the person in charge who should complete the change work. When the input is completed, the change content confirmation field 81 is added by clicking the add button 87.

  FIG. 8 is a diagram showing a change request inquiry result screen 9 which is a result of inquiring the items described in the change content confirmation column 81 of FIG. The change request inquiry result screen 9 includes a change request inquiry result confirmation column 91, a request button 92, a correction button 93, a cancel button 94, and a mouse pointer 95.

  In the change request inquiry result confirmation column 91, the business name related to the change request shown in the change content confirmation column 81 in FIG. “A1, a2” is displayed in the “Attached business” column, and “Person in charge” column shows “A” for business A, “B” for business a1, and “丙” for business a2 as appropriate personnel. The column “)” shows that the estimated man-hours are 60 hours for job A, 40 hours for job a1, 20 hours for job a2, and 120 hours in total. A person who requests a change in business clicks the request button 92 in consideration of such information and requests a change with this content. Then, the content of the change request is transmitted from the client 2 to the server 4, and a person in charge of the company or the like who is entrusted with the business confirms the content of the request and instructs the person in charge to execute the business.

  When the contents shown in the change request inquiry result confirmation column 91 are to be corrected, the correction button 93 is clicked to return to the change request screen 8 shown in FIG. Then, an inquiry is again made regarding the change request for the corrected content. The contents shown in the change request inquiry result confirmation column 91 may be directly editable. When canceling the change request, the user can click the cancel button 94 to return to the menu screen 5.

  Next, a series of processing performed between the client 2 and the server 4 when the server 4 is inquired about the work related to the change request will be described with reference to the flowchart of FIG.

  First, a person in charge of a company or the like entrusting the business edits the content of the change request on the change request screen 8 displayed on the client 2 (S1).

  When the inquiry button 83 is clicked (S2), the process proceeds to S4 and subsequent steps. If the inquiry button 83 is not clicked and the cancel button 84 is clicked (S3), the inquiry process is terminated and the menu screen 5 is restored.

  When the inquiry button 83 is clicked (S2), a task stored in the incidental task storage unit 423 is retrieved according to the period specified in the incidental task search range designation column 82 (S4). If incidental work is stored for the work related to the change request, the incidental work is included in the inquiry result.

  Next, with respect to the work related to the change request and the incidental work detected in S4, the work history storage unit 421 is searched for an execution history. It is detected as a person (S5) and included in the inquiry result. If the person in charge is not detected by the search, the search target may be appropriately expanded, for example, by including a person who performs the related work in the search target. Further, in detecting the person in charge, it is possible to take into account the circumstances such as whether the person has another schedule.

  Further, for the task related to the change request and the incidental task detected in S4, the task man-hour storage unit 424 is searched to calculate the man-hour (S6) and included in the inquiry result. In the present embodiment, the man-hours for each work stored in the work man-hour storage unit 424 are copied and the total value is included in the inquiry result. However, the calculation method changes depending on the specific contents of the change request. It may be included in the inquiry result as an estimated man-hour.

  The server 4 transmits a query result including the above information to the client 2. Then, the inquiry result is displayed on the change request inquiry result screen 9 displayed on the client 2 (S7).

  If the inquiry result needs to be corrected, the correction button 93 is clicked (S8), the process returns to the change request screen 8 and the change request is edited again (S1).

  When making a change request with the content of the inquiry result, the request button 92 is clicked (S9), and the change request content is transmitted to the server 4 (S10).

  FIG. 10 shows the supplementary task content 4231 stored in the supplementary task storage unit 423, which is referred to in the supplementary task search (S4). The incidental business content 4231 includes a “request date” field, a “business” field, and an “accompanying business” field. For example, it is stored that the incidental operations of the operation A are a1 and a2, and the request date is April 1, 2013. These pieces of information are stored when a business request is transmitted from the client 2 and the contents of the business request screen 6 are received by the server 4.

  Further, when performing the incidental work search (S4), the request date included in the incidental work content 4231 is referred to search for an incidental work that matches the period specified in the incidental work search range designation column 82. By limiting the search range in this way, even if a task incidental to a certain task changes due to a specification change or the like, only a recent incidental task becomes a search target.

  FIG. 11 is a diagram showing the business man-hour content 4241 stored in the business man-hour storage unit 424 that is referred to when the business man-hour is calculated (S6). The task man-hour content 4241 is a summary of man-hours for each task in units of time. In this embodiment, the man-hour is defined as the time required when one person in charge with an average ability performs all of the work. Therefore, for example, the man-hour of the job A is shown as 60 hours, but depending on the content of the change request for the job A, the change may be completed with a smaller man-hour. Therefore, the man-hours shown on the change request inquiry result screen 9 in the present embodiment are man-hours required when the work is completely redone, and indicate the maximum man-hours expected.

  The man-hour of each business may be calculated from the difference between the business completion date and the request date for each business stored in the business history storage unit 421, for example. In addition, a person in charge of a company or the like who has entrusted the work may set the work prior to the execution of the work.

  As described above, when a business change request is made from a business consignment company to a business consignment company and the server 4 receives the change request, the request contents are sent to the change history storage unit 422 and the business history storage unit 421 of the server 4. Is memorized. The process at that time will be described below.

  FIG. 12 is a flowchart showing a series of processes performed in the server 4 when the server 4 receives a business request or a change request.

  First, regardless of whether the request content is a new business request or a business change request, the request content is stored in the business history storage unit 421 (S11). Specifically, the request date, the requested business name, and the name of the person in charge of the business are stored as a new business history. The business completion date is stored when the business is completed.

  Then, the server 4 determines whether the accepted business is related to the change request (S12). Here, if the received business is not related to the change request, that is, if the new business is requested, the processing is terminated.

  If the received work is related to a change request, the request content is stored in the change history storage unit 422 (S13). Specifically, the request date, the requested business name, and the name of the person in charge of the business are stored as a new change history. When the business change is completed, the change completion date is stored.

  Then, in the “Related Work History” column of the change history, the related work history No. Fill in. A specific example of this field is shown in the next figure. In short, the work history newly stored in S11 is associated with the change history newly stored in S13.

  Similarly, the change history No. newly stored in S13 is stored in the “related change history” column of the business history newly stored in S11. Fill in. Thereby, the business history and the change history are linked to each other (S16). However, the correspondence relationship is not necessarily one-to-one, and a plurality of business histories may correspond to one change history. As shown in FIGS. 7 and 8, even if there is only one task related to the change request, there may be a plurality of incidental tasks, so the actual work performed will be more than the task related to the change request. Because there is.

  FIG. 13 shows the content of the change history screen 10 when the content change request shown in FIG. 8 is made on July 1, 2013. The change history screen 10 can be displayed by clicking the change history button 54 on the menu screen 5, and indicates the contents of the change history storage unit 422.

  The change history screen 10 includes a change history display field 101, a return button 102, and a mouse pointer 103. Here, the change history display column 101 includes a “request date” column, a “change completion date” column, a “business” column, a “person in charge” column, and a “related business history” column. In the present embodiment, “July 1, 2013”, which is the date when the change request is made, is entered in the “Request Date” column. In addition, “A” is entered in the “person in charge” column, and it can be read that the person in charge shown in the change request inquiry result screen 9 in FIG. In the “Related Work History” column, “Business History No. 7” is shown. When this character is clicked, for example, the job history screen 7 is jumped to by an HTML hyperlink. Clicking the back button 102 returns to the menu screen 5 in the same manner as other screens.

  FIG. 14 shows a business history screen 7 displayed when “business history No. 7” in the change request inquiry result screen 9 is clicked. The difference from the work history screen 7 shown in FIG. 7-9 is added.

  Business history No. Reference numeral 7 denotes a history of a job A that is a job related to the change request. “Change history No. 1” is entered in the “Related change history” column, and is linked to “Business history No. 7” in the “Related work history” column shown in FIG. Business history No. Reference numerals 8 and 9 denote business histories of a1 and a2 which are business incidental to business A. The person in charge of both tasks is the same as the person in charge shown in the change request inquiry result screen 9 in FIG. 8, and it can be read that the completion date of each job is later than the completion date of job A.

  Business history No. “Change history No. 1” is also entered in the “Related change history” column of 8 and 9, and is linked to “Business history No. 7” in the “Related job history” column displayed on the change history screen 10. Yes. As a result, the business history No. It can be read that the operations a1 and a2 of 8 and 9 are a series of operations performed in response to a change request for the operation A.

  As described above, the business request, the business change request, and the business history and the change history are associated in the commissioned business management system according to the present embodiment.

  1 commissioned business management system, 2 client, 3 communication network, 4 server, 5 menu screen, 6 business request screen, 7 business history screen, 8 change request screen, 9 change request inquiry result screen, 10 change history screen, 41 network connection Part, 42 storage part, 43 control part, 44 input part, 45 display part, 51 work request button, 52 change request button, 53 work history button, 54 change history button, 55 mouse pointer, 61 requested work confirmation column, 62 request Button, 63 Cancel button, 64 Business input field, 65 Add button, 66 Mouse pointer, 71 Business history display field, 72 Back button, 73 Mouse pointer, 81 Change content confirmation field, 82 Attached business search range designation field, 83 Person in charge Search range specification field, 84 inquiry button, 85 cancel button 86 Change input field, 87 Add button, 88 mouse pointer, 91 Change request inquiry result confirmation field, 92 Request button, 93 Modify button, 94 Cancel button, 95 Mouse pointer, 101 Change history display field, 102 Return button, 103 mouse Pointer, 421 Work history storage section, 422 Change history storage section, 423 Attached work storage section, 424 Work man-hour storage section, 4231 Attached work contents, 4241 Work man-hour contents.

Claims (7)

A consignment work management system including a first user device and a second user device,
The first user device is
Business request transmission means for sequentially transmitting a business request regarding a main business that is a main consignment business and one or a plurality of incidental business incidental thereto, to the second user device;
Inquiry request transmission means for transmitting an inquiry request relating to the main business to the second user device ;
Inquiry result receiving means for receiving an inquiry result relating to the main business from the second user device ;
Based on the inquiry result, comprising a business change request transmission means for transmitting a change request for the main business and the incidental business to the second user device,
The second user device is
Business request receiving means for sequentially receiving business requests related to the main business and the incidental business ;
Business history storage means for storing a plurality of business requests;
Inquiry request receiving means for receiving the inquiry request;
Based on the main job related to the received inquiry request, the job request related to the main job from the plurality of job requests stored in the job history storage means and satisfying a predetermined condition A search means for searching multiple times,
Job detection means for detecting a plurality of the incidental tasks related to the plurality of job requests searched by the search means;
Inquiry result transmission means for transmitting information on the detected plurality of incidental tasks to the first user device as the inquiry result;
A business change request receiving means for receiving a change request for the main business and the incidental business ;
And operational change history storing means for memorize the changes according to the change request of the business that the received,
Wherein the changes stored in the business change history storing means, for associating the stored operational in the operational history storage means corresponding to those said alteration further details, and the business association means,
A commissioned business management system characterized by comprising: The second user device is
A task detection means for detecting a task other than the task related to the change among the tasks performed in accordance with the change request for the task;
Delegated task management system according to claim 1, characterized in further comprise a number of steps calculated means to calculate the number of steps of operations are carried out with the change request before Symbol business. The business history storage means includes
Stores the work performed in response to the work request together with the person who performed the work,
The second user device is
Based on the work stored in the work history storage means and the person who performed the work, a work implementer detecting means for detecting a person who performs the work performed in response to the change request for the work,
The commissioned business management system according to claim 2, further comprising: The second user device is
When a job change request is received by the job change request receiving unit, the incidental job detected by the job detection unit, the man-hour calculated by the man-hour calculating unit, and the job performer detecting unit are detected. A business schedule transmission means for transmitting a person to the first user device;
The commissioned business management system according to claim 3, further comprising: The work detection means includes
Wherein among the stored business to business history storing means, it detects the ancillary operations based on the operation request that stored in a predetermined period of time,
The implementer detection means includes:
Of the work stored in the work history storage means and the person who executed the work, the work stored within a certain period of time and the work carried out in response to the change request for the work Detect who performs the
The commissioned business management system according to claim 4, wherein: The business change request transmission means includes:
Send the work to be performed in response to the change request for the work,
The business change request receiving means
Receiving a work to be performed in response to the change request for the work;
The commissioned business management system according to any one of claims 2 to 5, wherein: Computer
A business request receiving means for sequentially receiving a business request relating to a main business which is a main commissioned business and one or a plurality of incidental services attached thereto;
Business history storage means for storing a plurality of business requests;
A business change request receiving means for receiving a business change request;
Inquiry request receiving means for receiving the inquiry request;
Based on the main job related to the received inquiry request, the job request related to the main job from the plurality of job requests stored in the job history storage means and satisfying a predetermined condition Search means to search multiple times,
Job detection means for detecting a plurality of incidental jobs related to the plurality of job requests searched by the search means;
Inquiry result transmission means for transmitting the information related to the plurality of incidental services detected to the first user device as the inquiry result;
Business change history storing means for memorize the changes according to the change request of the business that the received,
Associating the change contents stored in the business change history storing means, said operation request stored in the operational history storage means corresponding to those said alteration further contents, business association means,
A program characterized by functioning as

Images