JP2007334639A - Procurement support system, procurement support method, and procurement support program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a procurement support system, a procurement support method, and a procurement support program capable of supporting the procurement of components. <P>SOLUTION: The procurement support system includes a procurement support server 1, and a procurement support database 2. The procurement support database 2 stores the present situation on the delivery delay for every delivery trouble element possibly causing any delivery delay trouble on the causes of any delivery troubles possibly causing delivery delay troubles of components to be procured. The procurement support server 1 sets the points according to the present situation on the delivery delay, calculates the risk points of the components from the set points, and determines whether a preventive action for preventing the delivery delay of the components is performed based on the calculated risk point of the components. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a procurement support system, a procurement support method, and a program.

  In general, in a company, a plurality of persons in charge procure parts independently, and report information on current procurement by, for example, weekly reports. However, there is a problem that it is difficult to understand who and how to deal with a problem part in the report by a weekly report or the like. In addition, in reports by weekly reports and the like, the response to similar products before reporting is insufficient. In order to solve these problems, various proposals have been made regarding the procurement of parts.

For example, Patent Document 1 discloses a quality information analysis support apparatus that can quickly improve part quality by sharing part quality information between an inspection department and a manufacturing department.
JP 2003-122817 A

  By the way, even if information relating to parts procurement is made into a database, for example, there is a risk that leakage, delay, etc. may occur due to variations in the judgment of individuals in charge of parts procurement. For this reason, provision of the system which can further support procurement of components is calculated | required so that management of the components in question may fully be performed.

  The present invention has been made in view of the above problems, and an object thereof is to provide a procurement support system, a procurement support method, and a program that can support procurement of parts.

In order to achieve the above object, a procurement support system according to the first aspect of the present invention includes:
Risk information storage means for storing risk information related to the risk of delay in delivery of parts to be procured;
Based on the risk information stored in the risk information storage means, a risk point calculation means for quantifying the delivery delay risk of the part and calculating the risk point of the part from the quantified delivery delay risk;
Based on the risk points of the parts calculated by the risk point calculation means, a determination means for determining whether to implement a precautionary measure for preventing a delay in delivery of the parts;
It is characterized by comprising.

The risk information has a delivery date problem element that may cause a delivery delay problem and a delivery date cause that may cause a delivery delay problem;
The risk information storage means stores, for each delivery date problem element, a current situation regarding delivery date delay for each delivery date problem cause,
The risk point calculation means may set points according to the current situation regarding the delivery date delay, and calculate a risk point of a part from the set points.

  When it is determined by the determination means that the preventive measure is to be implemented, a person-in-charge determination means for determining a person in charge of procuring the part as a person in charge of preventing the delay in delivery of the part more than a normal person in charge May be further provided.

The procurement support method according to the second aspect of the present invention is:
A risk information storage step for storing risk information related to a risk of delay in delivery of parts to be procured;
Based on the risk information stored in the risk information storage step, a risk point calculation step of quantifying the delivery delay risk of the part and calculating the risk point of the part from the quantified delivery delay risk;
A determination step for determining whether to implement a preventive measure for preventing a delay in delivery of the part based on the risk point of the part calculated in the risk point calculation step;
It is characterized by comprising.

The program according to the third aspect of the present invention is:
Computer
A risk information storage means for storing risk information relating to a risk of delay in delivery of parts to be procured;
Based on the risk information stored in the risk information storage means, a risk point calculation means for quantifying the delivery delay risk of the part and calculating the risk point of the part from the quantified delivery delay risk,
Discriminating means for discriminating whether or not to implement preventive measures for preventing delay in delivery of the part based on the risk point of the part calculated by the risk point calculating means,
It is made to function as.

  According to the present invention, it is possible to support procurement of parts.

  Hereinafter, a procurement support system, a procurement support method, and a program according to an embodiment of the present invention will be described.

FIG. 1 shows the configuration of the procurement support system of the present embodiment. As shown in FIG. 1, the procurement support system includes a procurement support server 1, a procurement support database 2, a communication network 3, and user terminals 4 (4 ₁ to 4 _n ) connected via the communication network 3. And.

  The procurement support server 1 is for performing various processes related to the procurement support system. FIG. 2 shows a configuration diagram of the procurement support server 1. As shown in FIG. 2, the procurement support server 1 includes a communication control unit 11, a process control unit 12, and a data storage unit 13.

  The communication control unit 11 is configured by a predetermined communication device such as a router, for example, and connects the procurement support server 1 and the communication network 3. For example, the communication control unit 11 receives various data (information) from the user terminal 4 via the communication network 3.

  The processing control unit 12 performs communication via the communication control unit 11 and processes various types of information. The process control unit 12 includes, for example, a CPU (Central Processing Unit), and executes various processes by executing an operation program read from the data storage unit 13.

  The data storage unit 13 includes a semiconductor memory, a magnetic disk recording device, and the like, and records various information and programs.

  The procurement support database 2 is a database (DB) that stores various types of information related to the procurement support system. FIG. 3 shows the configuration of the procurement support database 2. As shown in FIG. 3, the procurement support database 2 includes a user information DB 21, a parts information DB 22, an order information DB 23, a risk evaluation information DB 24, and an image information DB 25.

  The user information DB 21 is a database that stores information related to users of the procurement support system that procure parts. For example, as shown in FIG. 4, the user information DB 21 stores a user ID, name, title, e-mail address, password, and the like. Here, the user ID is user identification information. The password is a password for the user to log in to the procurement support system.

  The component information DB 22 is a database that stores information on procurable components. For example, as shown in FIG. 5, the component information DB 22 stores a component number, a component name, a manufacturer name, a supplier, and the like. In addition, in the parts information DB 22, for each part, the presence or absence of an element (delivery date problem element) that may cause a delivery delay problem described later, and a cause (delivery problem cause) that may cause the delivery delay problem ) Is stored.

  The ordering information DB 23 is a database that stores information on ordering (procurement) parts. For example, as shown in FIG. 6, the order information DB 23 stores an order number, a part number, a quantity, a person-in-charge ID, a supplier, a delivery date, progress information, and the like. In the progress information, information obtained from the negotiation status between the person in charge and the supplier regarding the delivery date of the part, for example, the negotiation date and time and the result (scheduled delivery date) with the supplier are stored.

  The risk evaluation information DB 24 is a database that stores information relating to risk evaluation of parts to be procured. The risk evaluation information DB 24 stores the current situation regarding the degree of delay, the frequency of delay, and the possibility of delay for each cause of delivery date problem. Causes of delivery date problems include a sudden increase in production, market tightness, production reduction / suspension, quality defects, and abolition. Delivery time problem factors include trouble predecessors, overseas products, custom-made products, special management parts, and the like.

  For example, FIG. 7 shows an example of the current situation regarding the degree of delay, the frequency of delay, and the possibility of delay when the cause of the delivery date problem is a sudden increase in production. As shown in FIG. 7, risk points corresponding to the respective situations are determined for the degree of delay, the frequency of delay, and the possibility of delay. The risk point is a numerical value of the risk of delay in delivery of parts. For example, in the case of delay, “1 week (1W)” is “1” points, and “1 month (1M)” is “3” points. “Several months (several M)” is defined as “5” points, and “Discontinued (discontinued)” is defined as “7” points. In the case of the delay frequency, “not” is defined as “0” points, “sometimes” is defined as “1” points, and “more” is defined as “3” points. In the case of the possibility of delay, “0” to “5” are set according to the possibility. Therefore, when the cause of the delivery date problem is a rapid increase in production and the delivery date issue element is the trouble predecessor, as shown in FIG. 7, the risk point is (degree of delay: “5”) + (frequency of delay: “3”) + (Possibility of delay: “3”) = “11” points.

  In the risk evaluation information DB 24, information as shown in FIG. 7 is stored for each cause of the delivery date problem. For this reason, a risk evaluation table as shown in FIG. 8 is created based on the information stored in the risk evaluation information DB 24. The risk evaluation table can convert risk information relating to the delivery date of parts into objective data (numericalization), and can reveal the risk relating to the delivery date of the parts. By using this risk evaluation table, risk points of parts can be obtained. For example, if the cause of the delivery date problem is "Rapid increase in production" or "Market tightness", and the part to be procured falls under the "Delivery trouble product" or "Overseas product" Risk points are (11 of sudden increase in production + 9) + (9 of market tightness + 7) = 36 points. This risk assessment table is used for risk assessment of parts in the risk assessment process described later.

  The image information DB 25 is a database that stores information constituting various images displayed in each process described later, and stores images of various materials and various forms for generating these images.

  The communication network 3 is a communication network such as the Internet, LAN (Local Area Network), and WAN (Wide Area Network) based on a predetermined communication protocol such as TCP / IP (Transmission Control Protocol / Internet Protocol).

  The user terminal 4 is composed of, for example, a computer having a communication function. The user terminal 4 is used, for example, for operation input in processing such as login, order information registration processing, progress information registration processing, and the like, as will be described later.

  According to the procurement support system configured as described above, since information related to ordering (procurement) parts is stored in the ordering information DB 23, information related to part procurement can be centrally managed in real time. In addition, information can be shared when each user views the information registered in the ordering information DB 23. For this reason, procurement of parts can be supported by this system.

  Next, a procurement support method using the procurement support system configured as described above will be described. Hereinafter, description will be made in the order of pre-registration, login, order information registration process, progress information registration process, order information display process, and risk evaluation process.

(Pre-registration)
In order for the user to use the procurement support system, it is necessary to register in advance in the procurement support system. First, the user transmits information such as the user's name, title, and e-mail address from the user terminal 4 to the procurement support server 1 via the communication network 3. Upon receiving information such as the user's name, the procurement support server 1 (processing control unit 12) issues a user ID and password, and transmits the user ID and password to the user terminal 4 by e-mail, for example. . Further, the processing control unit 12 registers the received predetermined information, user ID, and password in the user information DB 21. Thereby, the advance registration by the user is completed. An administrator of this system may be provided, and this administrator may perform user pre-registration.

(Login)
The user accesses the Web site provided by the procurement support server 1 from the user terminal 4 via the communication network 3 and inputs the received ID (login name) and password. If the processing control unit 12 recognizes that the user is a user from the transmitted login name and password, for example, the menu control information (HTML format information) as shown in FIG. 9 is read from the image information DB 25 and the user is read. And the menu screen is displayed on the user terminal 4. On the menu screen, as shown in FIG. 9, “order information registration” for registering order information in the order information DB 23, “progress information registration” for registering progress information in the order information DB 23, and orders registered in the order information DB 23 Menu columns such as “order information display” for displaying the contents of information are arranged. The user operates the user terminal 4 and clicks “Order Information Registration”, “Progress Information Registration”, etc. from this menu screen, thereby performing processing such as order information registration and progress information registration. It can be carried out.

(Order information registration process)
The order information registration process is a process for registering information related to part ordering. FIG. 10 is a flowchart for explaining the order information registration process. Hereinafter, a case where a user of this system (a person in charge of parts procurement) registers information related to part ordering will be described as an example. An administrator of this system may be provided, and this administrator may perform order information registration processing.

  First, the process control unit 12 reads the menu screen shown in FIG. 9 from the image information DB 25, transmits it to the user terminal 4, and displays the menu screen on the user terminal 4 (step S1). Next, the process control unit 12 determines whether or not “order information registration” is selected from the menu screen (step S2). That is, it is determined whether or not the user clicked “Register Order Information” from the menu screen. If the process control unit 12 determines that “order information registration” has not been clicked (step S2; No), the process ends.

  If it is determined that “order information registration” is clicked (step S2; Yes), the processing control unit 12 reads the registration screen shown in FIG. 11 from the image information DB 25, transmits it to the user terminal 4, and uses it. A registration screen is displayed on the user terminal 4 (step S3). The registration screen is provided with input fields such as an order number, a part number, and a quantity. The user can register the ordering information by operating the user terminal 4, inputting necessary items in the input field, and selecting (clicking) “Register”. Note that by selecting an item to be input and selecting (clicking) “list”, a list of items to be input to the item can be displayed.

  Next, the process control unit 12 determines whether or not “registration” is selected (step S4). When determining that “registration” is selected (step S4; Yes), the process control unit 12 stores the created order information in the order information DB 23 (step S5), and ends this process.

(Progress information registration process)
The progress information registration process is a process for registering information on the progress status of the ordered parts, and a person in charge of parts procurement (user) registers information (progress information) on the negotiation status with the supplier in the order information DB 23. It is processing. FIG. 12 is a flowchart for explaining the progress information registration process.

  First, the process control unit 12 reads out the menu screen shown in FIG. 9 from the image information DB 25, transmits it to the user terminal 4, and displays the menu screen on the user terminal 4 (step S11). Next, the process control unit 12 determines whether “progress information registration” is selected from the menu screen (step S12). If the process control unit 12 determines that “progress information registration” has not been clicked (step S12; No), the process ends.

  If it is determined that “progress information registration” is clicked (step S12; Yes), the process control unit 12 creates a list screen showing a list of order information registered in the order information DB 23, and the created list screen Is transmitted to the user terminal 4 to display a list screen on the user terminal 4 (step S13).

  Next, the process control unit 12 determines whether or not ordering information has been selected (step S14). When the process control unit 12 determines that the order information is selected (step S14; Yes), the information stored in the selected order information (order number, part number, quantity, person ID, delivery date, progress) Information etc.) is transmitted to the user terminal 4 and the selected order information is displayed on the user terminal 4 (step S15).

  The displayed order information is obtained by registering information such as an order number, a part number, and a quantity in each item of the registration screen. The user can register the progress information by operating the user terminal 4, inputting necessary items in the progress information input field, and selecting (clicking) “Register”.

  Next, the process control unit 12 determines whether or not “registration” is selected (step S16). When determining that “registration” is selected (step S16; Yes), the process control unit 12 stores the created progress information in the order information DB 23 (step S17).

  Subsequently, the process control unit 12 determines whether the created progress information includes information on the cause of the delivery date problem and the delivery date problem element (step S18). If the process control unit 12 determines that there is no information regarding the cause of the delivery date problem and the delivery date problem element (step S18; No), the process ends. If the processing control unit 12 determines that there is information on the cause of the delivery date problem and the delivery date problem element (step S18; Yes), the process control unit 12 adds information on the cause of the delivery date problem and the delivery date problem element to the corresponding part registered in the part information DB 22. Store (step S19), and this process ends.

  Thus, the latest progress information regarding the progress status of the ordered part is registered in the order information DB 23 by the user, so that the progress status of the ordered part can be easily managed.

(Order information display processing)
The order information display process is a process for displaying the order information registered in the order information DB 23. The order information display process is executed by substantially the same process as steps S11 to S15 described above, except for determining whether or not “display order information” is selected in step S12. By this processing, the user can know the contents of the order information registered in the order information DB 23 and the progress information (current situation).

(Risk assessment process)
The risk evaluation process is a process for evaluating a risk related to the delivery date of the order (procurement) part. Depending on the risk (risk points) evaluated by this risk evaluation process, various preventive measures such as setting and changing the person in charge, and advance ordering (advance arrangement) can be implemented. In the present embodiment, an example is given in which risk evaluation (risk point calculation) is performed when ordering information is registered in the ordering information DB 23 (before parts ordering), and a person in charge is determined according to the calculated risk point. explain. FIG. 13 is a flowchart for explaining the risk evaluation process.

  First, the process control unit 12 determines whether or not the order information is registered in the order information DB 23 (step S21). If it is determined that the order information is registered in the order information DB 23 (step S21; Yes), the process control unit 12 specifies a part related to the registered order information. (Step S22).

  Next, the process control unit 12 specifies the cause of the delivery date problem of the identified part and the delivery date problem element (step S23). In the present embodiment, the cause of the delivery date problem of the part and the delivery date problem element are registered in the parts information DB 22, and the process control unit 12 stores the identified parts stored in the parts information DB 22 for this part. Identify the cause of the delivery date problem and the delivery date problem element.

  Subsequently, the process control unit 12 calculates a risk point for the identified part based on the identified cause of the delivery date problem and the delivery date problem element (step S24). Specifically, a risk evaluation table as shown in FIG. 8 is created based on the information stored in the risk evaluation information DB 24, and the risk points of the identified parts are calculated using the created risk evaluation table. For example, if “Rapid increase in production” and “Market tightness” are specified as the cause of the delivery date problem, and “Precursor trouble product” and “Overseas production product” are specified as the delivery date problem factors, the risk of the identified parts The key points are (11) for the sudden increase in production / trouble predecessor products + (9) for the rapid increase in production / overseas production products) + (9) for the market tightness / trouble trouble products) + (market tightness / overseas production “7”) = “36” points of the product.

  Next, the process control unit 12 determines whether or not the calculated risk points of the parts are a predetermined number or more (step S25). If the process control unit 12 determines that the calculated risk point of the component is not equal to or greater than the predetermined number (step S25; No), the process controller 12 determines a normal person in charge as a person in charge (step S26). If the process control unit 12 determines that the calculated risk points of the parts are equal to or greater than the predetermined number (step S25; Yes), the person who is more likely to prevent (solve) the delivery date problem than the normal person in charge, for example, normal The person in charge of the person in charge is determined to be the person in charge (step S27). For example, when a normal person in charge does not have a job title, a supervisor such as a section manager or a section manager is determined as the person in charge. Then, the process control unit 12 registers the determined person in charge in the order information DB 23 (Step S28), and ends this process.

  As described above, the person in charge of a part with a high risk point, that is, a part with a high possibility of causing a problem in the delivery management of the part, is set as a supervisor of a normal person in charge. For this reason, it becomes easier to solve the delivery date problem earlier than the case where a normal person in charge is assigned to the person in charge. By automatically determining such a person in charge, procurement of parts can be facilitated. For this reason, procurement of parts can be supported by this system.

  As described above, according to the present embodiment, since information related to ordering (procurement) parts is stored in the ordering information DB 23, information related to part procurement can be centrally managed in real time. In addition, information can be shared when each user views the information registered in the ordering information DB 23. For this reason, procurement of parts can be supported by this system.

  Further, according to the present embodiment, since the risk point related to the delivery date of the component is calculated based on the cause of the delivery date problem and the delivery date problem element, the risk related to the delivery date of the component can be made obvious. For this reason, procurement of parts can be supported by this system.

  Furthermore, according to the present embodiment, since parts having a high risk point are used, it becomes easier to solve the delivery date problem earlier than a case where a normal person in charge is used as a person in charge. For this reason, procurement of parts can be supported by this system.

  In addition, this invention is not restricted to said embodiment, A various deformation | transformation and application are possible. Hereinafter, other embodiments applicable to the present invention will be described.

  In the above-described embodiment, the present invention has been described as an example in the case where the person in charge is determined according to the calculated risk point, but it is only necessary to be able to implement a preventive measure against the delivery delay of the ordered part, For example, the order date may be determined so that the order date is advanced (preceding order). Further, the ordering period may be extended.

  In the above-described embodiment, the present invention has been described as an example in which the person in charge is determined to be the supervisor of the person in charge as a precautionary measure against the delay in delivery of parts. For example, when the calculated risk point is 50 or more, May be the chief of staff, and in the case of 70 or more, the section manager may be the person in charge. In addition, the person in charge to be determined does not have to be a supervisor of a person in charge of a normal person as long as it can prevent (solve) a delivery date problem.

  In the above embodiment, the present invention has been described by taking as an example the case where the person in charge is determined by performing the risk evaluation process before ordering. However, for example, the risk evaluation process may be performed after ordering. The risk evaluation process after ordering can be performed at any time, but is preferably performed when the progress information has not progressed over a predetermined period. FIG. 14 is a flowchart for explaining the risk evaluation process in such a case.

  In this case, first, the process control unit 12 determines whether or not the progress information has progressed for a predetermined period or longer (step S31). When it is determined that the progress information has progressed within the predetermined period (step S31; No), the process control unit 12 ends this process. When it is determined that the progress information has not progressed for a predetermined period or longer (step S31; Yes), the process control unit 12 calculates the risk point of the component as in the above-described steps S22 to S25, and calculates the risk of the calculated component. It is determined whether or not there are a predetermined number of risk points (step S25). When the process control unit 12 determines that the calculated risk point of the component is not equal to or greater than the predetermined number (step S25; No), the process ends. If the process control unit 12 determines that the calculated risk points of the parts are equal to or greater than the predetermined number (step S25; Yes), the supervisor of the person in charge is changed to a person in charge (step S32), and the changed person in charge is ordered information. Registration in the DB 23 (step S33), and this process ends. Also in this case, by changing the person in charge to, for example, a boss or the like in accordance with the evaluated risk point, it is possible to obtain the same effect as when risk assessment processing is performed before ordering. Furthermore, regarding the procurement of parts, it is possible to provide support corresponding to changes in the situation after ordering parts.

  Further, in the risk evaluation process after ordering, for example, as shown in FIG. 15, even if the calculated risk points of the parts are not equal to or greater than a predetermined number (step S25; No), the progress information progresses for a predetermined period or more. If the progress information has not progressed for a predetermined period or longer (step S41: Yes), the supervisor in charge is changed to the person in charge (step S32), and the changed charge A person may be registered in the order information DB 23 (step S33). In this way, even if the calculated risk points are not equal to or greater than a predetermined number, it may be possible to implement preventive measures against delays in delivery of ordered parts.

  The risk evaluation process is not limited to the case where the risk evaluation process is performed either before or after the ordering, and may be performed both before the ordering and after the ordering. Further, the number of executions of the risk evaluation process after ordering is not limited to one time, and may be performed a plurality of times.

  Further, in the risk evaluation process after ordering, as a preventive measure against the delivery delay, for example, an email to confirm the delivery date of the part may be transmitted to the person in charge. In this case, when the process control unit 12 determines that the preventive measure against the delivery delay is to be implemented (for example, step S41: Yes), the process control unit 12 specifies the mail address of the person in charge from the user mail address registered in the user information DB 21. Then, an e-mail confirming the delivery date of the parts subjected to the risk evaluation process is transmitted to the specified e-mail address.

  In the above embodiment, the risk assessment table is created based on the risk assessment information DB 24 in which the degree of delay, the frequency of delay, and the possibility of delay are stored for each cause of delivery date problem. Although the present invention has been described by taking the case where risk points are calculated using an evaluation table as an example, risk information on the delivery date of the parts to be procured can be converted (quantified) into objective data, and the risk points of the parts can be calculated Any risk assessment table may be created for each cause of delivery date problem based on the current situation regarding the possibility of delay.

  In the above embodiment, in the progress information registration process, the present invention has been described by taking as an example the case of storing (registering) information regarding the cause of the delivery date problem and the delivery date problem element. Good.

  The procurement support server 1 according to the embodiment of the present invention can be realized using a normal computer system, not a dedicated system. For example, the procurement support server 1 configured to execute the above-described processing is configured by installing the program from a recording medium (flexible disk, CD-ROM, etc.) storing the program for executing the above-described processing in a general-purpose computer. can do.

  The means for supplying these programs is arbitrary. In addition to being able to be supplied via a predetermined recording medium as described above, for example, it may be supplied via a communication line, a communication network, a communication system, or the like. In this case, for example, the program may be posted on a bulletin board (BBS) of a communication network and provided by superimposing it on a carrier wave via the network. Then, the above-described processing can be executed by starting the program thus provided and executing it in the same manner as other application programs under the control of the OS.

It is a figure which shows the structure of the procurement assistance system which concerns on embodiment of this invention. It is a figure which shows the structure of the procurement assistance server of FIG. It is a figure which shows the structure of the procurement assistance database of FIG. It is a figure which shows an example of a user information database. It is a figure which shows an example of a components information database. It is a figure which shows an example of an order information database. It is a figure which shows an example of a risk evaluation information database. It is a figure which shows an example of a risk evaluation table. It is a figure which shows an example of a menu screen. It is a flowchart for demonstrating order information registration processing. It is a figure which shows an example of a registration screen. It is a flowchart for demonstrating a progress information registration process. It is a flowchart for demonstrating a risk evaluation process. It is a flowchart for demonstrating the other example of a risk evaluation process. It is a flowchart for demonstrating the other example of a risk evaluation process.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Procurement support server 2 Procurement support database 3 Communication network 4 User terminal 11 Communication control part 12 Processing control part 13 Data storage part 21 User information database 22 Parts information database 23 Ordering information database 24 Risk evaluation information database 25 Image information database

Claims (5)

Risk information storage means for storing risk information related to the risk of delay in delivery of parts to be procured;
Based on the risk information stored in the risk information storage means, a risk point calculation means for quantifying the delivery delay risk of the part and calculating the risk point of the part from the quantified delivery delay risk;
Based on the risk points of the parts calculated by the risk point calculation means, a determination means for determining whether to implement a precautionary measure for preventing a delay in delivery of the parts;
A procurement support system characterized by comprising: The risk information has a delivery date problem element that may cause a delivery delay problem and a delivery date cause that may cause a delivery delay problem;
The risk information storage means stores, for each delivery date problem element, a current situation regarding delivery date delay for each delivery date problem cause,
2. The procurement support system according to claim 1, wherein the risk point calculation unit sets points according to a current situation regarding the delivery delay, and calculates a risk point of a part from the set points.   When it is determined by the determination means that the preventive measure is to be implemented, a person-in-charge determination means for determining a person in charge of procuring the part as a person in charge of preventing the delay in delivery of the part more than a normal person in charge The procurement support system according to claim 1, further comprising: A risk information storage step for storing risk information related to a risk of delay in delivery of the parts to be procured;
Based on the risk information stored in the risk information storage step, a risk point calculation step of quantifying the delivery delay risk of the part and calculating the risk point of the part from the quantified delivery delay risk;
A determination step for determining whether to implement a preventive measure for preventing a delay in delivery of the part based on the risk point of the part calculated in the risk point calculation step;
A procurement support method characterized by comprising: Computer
A risk information storage means for storing risk information relating to a risk of delay in delivery of parts to be procured;
Based on the risk information stored in the risk information storage means, a risk point calculation means for quantifying the delivery delay risk of the part and calculating the risk point of the part from the quantified delivery delay risk,
A discriminating means for discriminating whether or not to implement a precautionary measure for preventing a delay in delivery of the part based on the risk point of the part calculated by the risk point calculating means,
Program to function as.

Images