JP2018120532A - Delivery date proposal device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a sufficient response to a customer when a scheduled delivery date does not satisfy a requested delivery date requested by the customer.SOLUTION: A delivery date proposal device includes a determination unit and a suggestion unit. The determination unit determines whether the calculated scheduled delivery date meets the requested delivery date, or not, on the basis of a requested member which is a member of a product requested by a customer and the requested number which is the number of products. The proposal unit generates a change proposal in which the request of the customer is changed so that the scheduled delivery date approaches the requested delivery date, if the scheduled delivery date does not satisfy the requested delivery date.SELECTED DRAWING: Figure 1

Description

  Embodiments relate to a delivery date proposal device.

  2. Description of the Related Art A technique for calculating a scheduled delivery date of a product based on the configuration and number of components of a product received from a customer in order assembly production or the like is known.

JP2013-205923A JP 2003-85346 A JP 2004-157922 A

  However, when the calculated scheduled delivery date does not satisfy the requested delivery date requested by the customer, there is a problem that the response to the customer is insufficient.

  In order to solve the above-described problems and achieve the object, the delivery date proposal device of the embodiment includes a determination unit and a proposal unit. The determination unit determines whether or not a scheduled delivery date calculated based on a requested member that is a member of a product requested by a customer and a requested number of products that is the number of products satisfies the requested delivery date. When the planned delivery date does not satisfy the required delivery date, the proposing unit generates a change proposal in which a customer request is changed so that the planned delivery date approaches the requested delivery date.

FIG. 1 is an overall configuration diagram illustrating a delivery date proposal system according to an embodiment. FIG. 2 is a diagram illustrating an example of a requested product table indicating the contents of products requested by a customer. FIG. 3 is a diagram showing an example of a product specification table corresponding to the required product table shown in FIG. FIG. 4 is a diagram illustrating an example of a member table. FIG. 5 is a diagram illustrating an example of the item table. FIG. 6 is a diagram showing an example of a required manufacturing plan for the required product table. FIG. 7 is a diagram illustrating an example of the change history table. FIG. 8 is a diagram illustrating an example of a proposed manufacturing plan based on a proposal in which the specification indicated by the required product table is changed. FIG. 9 is a flowchart of the proposal process executed by the delivery date proposal device. FIG. 10 is a flowchart of selection item setting processing executed by the proposal unit. FIG. 11 is a flowchart of the member proposal process. FIG. 12 is a flowchart of the number proposal process. FIG. 13 is a flowchart of the cost proposal process. FIG. 14 is a block diagram illustrating a hardware configuration of a computer that functions as a part of the delivery date proposal device.

  Similar components are included in the following exemplary embodiments and modifications. Therefore, below, the same code | symbol is attached | subjected to the same component, and the overlapping description is partially abbreviate | omitted. Portions included in the embodiments and modifications can be configured by replacing corresponding portions in other embodiments and modifications. In addition, the configuration, position, and the like of the parts included in the embodiments and modifications are the same as those in the other embodiments and modifications unless otherwise specified.

<Embodiment>
FIG. 1 is an overall configuration diagram illustrating a delivery date proposal system 10 according to an embodiment. The delivery date suggestion system 10 is configured to meet customer requirements for a planned delivery date calculated from product specifications (hereinafter referred to as required specifications) including product components required by customers, the number of products, and product costs. If the delivery date is not met, the system generates a change proposal different from the required specification and provides it to the customer. An example of a product is an industrial computer.

  As shown in FIG. 1, the delivery date proposal system 10 includes one or a plurality of ordering devices 12 and a delivery date proposal device 14. The delivery date proposal device 14 is connected to one or a plurality of ordering devices 12 through a network 16 such as the Internet so that information can be transmitted and received.

  The ordering device 12 is, for example, a computer. The ordering device 12 is owned by a customer who orders an industrial computer, for example. The ordering device 12 includes an ordering side control unit 20, an ordering side storage unit 22, an ordering side display device 24, and an ordering side input device 26.

  The ordering side control unit 20 is, for example, a hardware processor such as a CPU (Central Processing Unit). The ordering side control unit 20 has various functions by, for example, reading an ordering program stored in the ordering side storage unit 22. Part or all of the functions of the order-side control unit 20 may be configured by hardware such as a circuit including an ASIC (Application Specific Integrated Circuit).

  The ordering side control unit 20 acquires information from the delivery date proposal device 14 and the ordering side input device 26. The ordering side control unit 20 transmits information to the delivery date proposing device 14 and the ordering side display device 24. For example, the ordering side control unit 20 acquires the required specification of the product requested by the customer via the ordering side input device 26. The ordering side control unit 20 generates a required product table 50 corresponding to the required specifications. The requested product table 50 includes, for example, a configuration set indicating a configuration of a plurality of members (hereinafter referred to as requested members) of a product requested by a customer, the number of requested products (hereinafter referred to as requested number), and a delivery date (hereinafter referred to as requested product). (Required delivery date) and required specifications such as required product cost (required cost) may be included. The ordering side control unit 20 stores the requested product table 50 in the ordering side storage unit 22 and transmits it to the delivery date proposal device 14. Further, when the scheduled delivery date calculated by the delivery date proposing device 14 does not satisfy the requested delivery date of the customer, the ordering side control unit 20 delivers the item table 56 including one or a plurality of items indicating the product member, the number, the cost, etc. Obtained from the proposal device 14. The ordering side control unit 20 displays the item table 56 on the ordering side display device 24, and acquires the items of the item table 56 selected by the customer via the ordering side input device 26. The ordering side control unit 20 transmits the item selected by the customer to the delivery date proposal device 14 as a selection item.

  The order-side storage unit 22 is a storage device including a ROM (Read Only Memory), a RAM (Random Access Memory), an HDD (Hard Disk Drive), an SSD (Solid State Drive), and the like. The ordering side storage unit 22 stores an ordering program executed by the ordering side control unit 20, information necessary for executing the ordering program, and information generated by executing the ordering program. The ordering side storage unit 22 stores, for example, a requested product table 50 indicating product specifications requested by the customer.

  The order-side display device 24 is a display device such as a liquid crystal display device with a speaker capable of outputting images and sounds.

  The order-side input device 26 is an input device such as a keyboard, a mouse, and a touch panel that accepts input from a user such as a customer.

  The delivery date proposal device 14 is, for example, a computer. The delivery date proposal device 14 is installed, for example, in a manufacturer that performs order production. The delivery date proposal device 14 includes a proposal side control unit 30, a proposal side storage unit 32, a proposal side display device 34, and a proposal side input device 36.

  The suggestion-side control unit 30 is a hardware processor such as a CPU (Central Processing Unit), for example. The proposal side control unit 30 includes a determination unit 40 and a proposal unit 42. The suggestion-side control unit 30 has the functions of the determination unit 40 and the suggestion unit 42 by, for example, reading a proposal program 46 stored in the proposal-side storage unit 32. Part or all of the determination unit 40 and the suggestion unit 42 may be configured by hardware such as a circuit including an ASIC (Application Specific Integrated Circuit).

  The determination unit 40 receives the requested product table 50 from the ordering device 12 via the network 16 and stores it in the proposal-side storage unit 32. The determination unit 40 generates a product specification table 52 generated by adapting to its own processing from the required product table 50 and stores the product specification table 52 in the proposal-side storage unit 32. The determination unit 40 calculates a requested member and a requested number of products requested by the customer indicated by the requested product table 50 or the product specification table 52, and a scheduled delivery date that is a schedule for delivering the product requested by the customer. For example, the determination unit 40 determines the scheduled delivery date based on the member table 54 indicating the stock status of the member and the in-process information 64 indicating the status of the worker who performs the assembly of the product together with the requested number and the requested number. May be calculated. The determination unit 40 compares the scheduled delivery date with the requested delivery date, and determines whether the scheduled delivery date satisfies the requested delivery date, that is, whether the product delivery is in time for the requested delivery date. The determination unit 40 outputs an unmatch signal to the proposal unit 42 when the scheduled delivery date does not satisfy the requested delivery date.

  When the planned delivery date does not satisfy the required delivery date, the proposing unit 42 obtains an unmatch signal, and sends a customer request (that is, requested member, requested number, requested cost, etc.) so as to bring the planned delivery date closer to the requested delivery date. Generate a modified change proposal.

  Specifically, when the planned delivery date does not satisfy the requested delivery date and the unmatch signal is acquired from the determination unit 40, the proposal unit 42 receives one or more items indicating the product member, the number, the cost, and the like via the network 16. Is transmitted to the ordering device 12.

  The proposing unit 42 acquires selection item information indicating one or more selection items selected by the customer from one or more items included in the item table 56 from the ordering device 12. The proposing unit 42 generates a change proposal including a member selected by the customer indicated by one or a plurality of selection items, a requested member corresponding to the number or cost, a requested number or requested cost so that the scheduled delivery date approaches the requested delivery date. . The proposing unit 42 may generate a change history table 60 that is a history of past change proposals and store it in the proposing side storage unit 32. When the proposal unit 42 acquires selection item information indicating no selection item from the ordering device 12, the proposal unit 42 may set a selection item and generate a change proposal based on the change history table 60.

  For example, when the customer's selection item indicates one of the product members, the proposal unit 42 realizes the basic configuration so that the planned delivery date approaches the required delivery date while maintaining the basic configuration that is the configuration of the customer's product. The change proposal including the changed member in which the detailed configuration of the requested member is changed is generated. In this case, the proposing unit 42 refers to the basic configuration and the detailed configuration of the member table 54 and selects the changed member.

  When the customer's selection item indicates the number of products, the proposing unit 42 calculates the number of changed products that can be manufactured by the requested delivery date out of the requested number of products of the customer so that the scheduled delivery date approaches the requested delivery date. Then, a change proposal including the number of changes is generated.

  When the customer's selection item indicates the cost of the product, the proposing unit 42 generates a change proposal including the change cost obtained by changing the cost of the product so that the scheduled delivery date approaches the requested delivery date. For example, the proposing unit 42 calculates the additional cost required for a part of the required number of units that can be manufactured by the required delivery date or the additional cost for manufacturing one unit by the required delivery date as the change cost.

  Thereby, the proposal part 42 produces | generates the change proposal containing at least any one of a change member, the number of change, and a change expense. Moreover, the proposal part 42 may produce | generate the change proposal containing multiple change members, the number of change, and change cost, when a several selection item is received. The proposal unit 42 transmits the change proposal to the ordering device 12 via the network 16.

  The proposal-side storage unit 32 is a storage device including a ROM (Read Only Memory), a RAM (Random Access Memory), an HDD (Hard Disk Drive), an SSD (Solid State Drive), and the like. The suggestion-side storage unit 32 stores a program executed by the proposal-side control unit 30, information necessary for executing the program, and information generated by executing the program. For example, the proposal-side storage unit 32 stores a proposal program 46 executed by the proposal-side control unit 30. The proposal-side storage unit 32 stores a required product table 50, a product specification table 52, a member table 54, a change history table 60, and in-process information 64 necessary for executing the proposal program 46. The work-in-progress information 64 includes information such as a manufacturing plan including information on a worker who assembles an already ordered product and information on members of the ordered product. The suggestion-side storage unit 32 stores an item table 56, a required manufacturing plan 58, a change history table 60, and a proposed manufacturing plan 62 that are generated or updated by executing the proposal program 46.

  The proposal-side display device 34 is a display device such as a liquid crystal display device with a speaker capable of outputting images and sounds.

  The proposal side input device 36 is, for example, an input device such as a keyboard, a mouse, and a touch panel that accepts an input from a user such as a contractor.

  FIG. 2 is a diagram illustrating an example of a requested product table 50 indicating the contents of products requested by customers. When the ordering device 12 receives the content of the product to be ordered from the customer, the ordering device 12 generates a requested product table 50 as shown in FIG. 2, for example. The required product table 50 may include a customer name indicating itself, a configuration set indicating the configuration of members requested regarding the OS, memory, and the like, a required number of ordered products, a required delivery date, and a required cost. It should be noted that the format of the required product table 50 such as information arrangement, type, and number may be changed as appropriate.

  FIG. 3 is a diagram showing an example of a product specification table 52 corresponding to the required product table 50 shown in FIG. When the determination unit 40 acquires the requested product table 50 illustrated in FIG. 2, the determination unit 40 generates the product specification table 52 illustrated in FIG. 3 and stores the product specification table 52 in the proposal-side storage unit 32. The determination unit 40 may acquire the product specification table 52 shown in FIG. 3 from the ordering device 12 and store it in the proposal-side storage unit 32. The determination unit 40 generates a product specification table 52 including, for example, item numbers, request items, and required specifications. The determination unit 40 registers a number for identifying each required item and a set of required specifications as an item No. The determination unit 40 registers items such as the number of products, the names of members included in the product, and the cost of the product as request items. The member name is a name of a member constituting a product such as an OS (Operating System), a memory, an HDD, a keyboard, and a mouse. The determination unit 40 associates the customer's requirement specifications with each requirement item and registers the requirement specifications in the basic configuration, first detailed configuration,..., And Nth detailed configuration of the required product table 50. The basic configuration indicates contents that are not changed in the change proposal among the required specifications of the product. The detailed configuration indicates the content to be changed in the change proposal among the required specifications of the product. Of the plurality of detailed configurations, the first detailed configuration has the highest importance, and the Nth detailed configuration has the lowest importance. Therefore, when changing the detailed configuration, the proposing unit 42 sequentially changes from the Nth detailed configuration. Specifically, the determination unit 40 registers the requested number requested by the customer in the basic configuration of the requested specification of the number. The determination unit 40 registers the contents of the members such as capacity and function requested by the customer in the basic configuration and detailed configuration of the required specifications of each member. The basic configuration of the member is, for example, the function of the product. The detailed configuration of the member is the detail of the configuration for realizing the function of the product indicated by the basic configuration. The determination unit 40 registers the cost of the product requested by the customer in the basic configuration of the cost requirement specification. Note that the determination unit 40 does not register the required specifications in the detailed configuration of the number and cost.

  FIG. 4 is a diagram illustrating an example of the member table 54. As shown in FIG. 4, the member table 54 includes a member ID, a member name, a basic configuration, a first detailed configuration,..., An Nth detailed configuration, a component code, and an accessory flag. The member ID is an ID for identifying member information including a member name, a basic configuration, a first detailed configuration,..., An Nth detailed configuration, a part code, and an accessory flag. The member name, basic configuration, first detailed configuration,..., Nth detailed configuration are the same as the required items, basic configuration, first detailed configuration,. For example, when the customer requests 4 GB as the basic configuration of the memory and two 2 GB as the detailed configuration, the determination unit 40 selects the member ID “B006”. The part code is a code that identifies a part for realizing a detailed configuration. The stock status indicates the number of parts in stock. The number of members indicated by the stock status may be a value calculated by subtracting the number of parts necessary for another product that has already been ordered from the current number of stocks. The determination unit 40 extracts the part code and the inventory status based on the selected member ID “B006”. The determination unit 40 calculates a scheduled delivery date based on the inventory status and the in-process information 64. The accessory flag is a flag for determining whether or not a member can be delivered even if it is deleted from the product. For example, the accessory flag of a member that cannot be deleted from the product such as the OS, the memory, and the HDD is set to “0”. On the other hand, an accessory flag of a member that can be deleted from a product such as a mouse or a keyboard is set to “1”.

  FIG. 5 is a diagram illustrating an example of the item table 56. When the determination unit 40 determines that the scheduled delivery date does not satisfy the customer's requested delivery date, the proposal unit 42 generates the item table 56 illustrated in FIG. 5 and transmits it to the ordering device 12. The proposing unit 42 generates an item table 56 including one or more item numbers extracted from the product specification table 52 and one or more request items. The proposing unit 42 displays an item table 56 including one or more request items, and accepts the selected request item as a selection item from the customer.

  FIG. 6 is a diagram illustrating an example of the required production plan 58 for the required product table 50. If the planned delivery date does not satisfy the required delivery date, the proposing unit 42 may generate the required production plan 58 shown in FIG. 6 and transmit it together with the item table 56 to the ordering device 12. Specifically, the proposing unit 42 refers to the production plan of the already ordered product included in the work-in-progress information 64, the inventory status of the member table 54, etc. The required production plan 58 is generated in which a period in which the product can be tested, a period for preparing the shipment of the product, a period for completing the shipment of the product, and the like are described on the calendar. In the example shown in FIG. 6, since the requested delivery date is September 12, and the completion of shipment is September 19, the customer cannot meet the delivery date by referring to the requested production plan 58. Can be recognized.

  FIG. 7 is a diagram illustrating an example of the change history table 60. As shown in FIG. 7, the proposing unit 42 generates or updates a change history table 60 that indicates a history of changes by selection items received from the ordering device 12. Specifically, the suggestion unit 42 assigns a history number to each change history. The proposal unit 42 includes, in the history No., the name of the customer who has selected the selection item, the selection item No. that is the item No. selected by the customer or the proposal unit 42 in the past, the selection date that is the date of selection of the selection item, and the customer Associates a result indicating whether the proposal has been accepted or rejected by the choice.

  FIG. 8 is a diagram illustrating an example of a proposed manufacturing plan 62 based on a proposal in which the specification indicated by the required product table 50 is changed. When the proposal unit 42 acquires the unmatch signal, the proposal unit 42 generates a change proposal including the content of changing the product specification based on the selection item selected by the customer, and based on the change proposal, the proposal manufacturing shown in FIG. A plan 62 may be generated. For example, when the customer selects the number of items whose item number is “1” and the memory whose item number is “3” as selection items, the proposing unit 42 changes the number of required units that can be manufactured by the requested delivery date. Then, a change proposal including another member of a memory having a different detailed configuration as a change member while maintaining the basic configuration is generated. Based on the proposed change, the proposing unit 42 describes the schedule for start of construction and testing on the calendar, and describes the number of changes that can be manufactured on September 12, which is the required delivery date, on the date of the calendar. A proposal manufacturing plan 62 shown in FIG.

  FIG. 9 is a flowchart of the proposal process executed by the delivery date proposal device 14. The proposal-side control unit 30 of the delivery date proposal device 14 reads the proposal program 46 to execute a flowchart of the proposal process.

  As shown in FIG. 9, in the proposal process, the determination unit 40 generates or obtains the product specification table 52 shown in FIG. 3 and stores it in the suggestion storage unit 32 (S102). For example, the determination unit 40 acquires the required product table 50 as illustrated in FIG. 2 from the ordering apparatus 12 and generates a product specification table 52 corresponding to the required product table 50. The determination unit 40 may acquire the product specification table 52 from the ordering device 12.

  The determination unit 40 calculates a scheduled delivery date based on the member table 54, the product specification table 52, and the in-process information 64 shown in FIG. 4 (S104). For example, the determination unit 40 calculates the number of parts that can be used for the product, the number of workers, and the like based on the inventory status of the members constituting each member indicated by the member table 54 and the number of workers indicated by the in-process information 64. To calculate the estimated delivery date. For example, in the required product table 50 shown in FIG. On the other hand, the stock status of the member ID “B006” corresponding to the memory (the basic configuration is 4 GB and the detailed configuration is 2 GB) shown in the product specification table 52 shown in FIG. 3 is 20 in the member table 54 shown in FIG. It has become. The arrival date of the memory is August 31. In this case, the determination unit 40 calculates, for example, September 19 as the scheduled delivery date.

  The determination unit 40 determines whether or not the calculated scheduled delivery date satisfies the requested delivery date of the customer in the requested product table 50 (S106). When determining that the scheduled delivery date satisfies the requested delivery date (S106: Yes), the determination unit 40 ends the proposal process.

  When determining that the scheduled delivery date does not satisfy the requested delivery date (S106: No), the determination unit 40 outputs an unmatch signal to the proposal unit 42 (S108). When the scheduled delivery date is September 19 and the requested delivery date is September 12, the determination unit 40 determines that the scheduled delivery date does not satisfy the requested delivery date.

  When obtaining the unmatch signal, the proposing unit 42 extracts the item number and the request item from the product specification table 52 stored in the proposing side storage unit 32, generates the item table 56 shown in FIG. (S110). In this case, the proposing unit 42 may generate a required production plan 58 shown in FIG. 6 and transmit it to the ordering device 12 together with the item table 56. For example, the proposing unit 42 describes the required production plan 58 as a start preparation period, which is a period until the insufficient memory is obtained.

  In the ordering device 12, when the ordering control unit 20 acquires the item table 56, the “no selection button” is displayed on the ordering display device 24 together with the item table 56. When the ordering device 12 acquires the required manufacturing plan 58 shown in FIG. 6 together with the item table 56, the ordering device 12 may display the required manufacturing plan 58 together with the item table 56 on the ordering side display device 24. The ordering side control unit 20 transmits selection item information indicating a selection item corresponding to the item No input by the customer via the ordering side input device 26 to the delivery date proposing device 14. The selection item information transmitted by the ordering side control unit 20 includes “no selection” when the customer selects the no selection button.

  The proposing unit 42 is in a standby state until selection item information is received from the ordering device 12 (S112: No). When the proposal unit 42 receives the selection item information from the ordering apparatus 12 (S112: Yes), the proposal unit 42 executes a selection item setting process for setting a selection item that is an item to be changed in the change proposal (S114).

  FIG. 10 is a flowchart of the selection item setting process executed by the proposing unit 42. As shown in FIG. 10, in the selection item setting process, the proposing unit 42 determines whether or not there is a selection item in the selection item information (S202). For example, when the customer selects one or a plurality of selection items from the item table 56, the proposing unit 42 determines that there is a selection item selected by the customer in the selection item information (S202: Yes), and the customer selects A selection item is set as a selection item (S204).

  For example, when the customer operates the “no selection button” or the like, the proposing unit 42 determines that there is no selection item in the selection item information (S202: No), and determines whether or not this customer is the first customer to place an order. Determination is made (S206). For example, the proposing unit 42 determines whether or not this customer is the first customer to place an order depending on whether or not the customer name shown in the requested product table 50 shown in FIG. 2 exists in the customer name in the change history table 60 shown in FIG. It may be determined.

  The proposal unit 42 determines that the current customer is not the first customer to order when the current customer is a customer who has been ordered before and the customer name of the customer exists in the change history table 60 (S206: No), selection items are set from the change history of the customer in the change history table 60 (S208). For example, in the example of the change history table 60 shown in FIG. 7, when the current customer is company A, the suggestion unit 42 has the history Nos. “1” and “3” are the same selection item No. Items No. “1”, “3”, “5” associated with the history No. are set as selection items.

  If the customer name of the customer does not exist in the change history table 60, the proposing unit 42 determines that the customer is the first customer to place an order (S206: Yes), and all the change histories that the change history table 60 has. Selection items are set from the table 60 (S210). For example, in the example of the change history table 60 shown in FIG. 7, the suggestion unit 42 associates the history No. with “2”, “4”, and “5” because they are the same selection item No. The selected item Nos. “1” and “3” are selected as selection items.

  When the suggestion unit 42 sets a selection item in any of steps S204, S208, and S210, the selection item setting process ends.

  Returning to FIG. 9, the proposing unit 42 determines whether or not the selection item includes a member (S116). When the proposing unit 42 determines that the selected item includes any member (S116: Yes), the member proposing process for generating a change proposal including a change member or the like in which the request member corresponding to the member is changed to another member. Is executed (S118).

  FIG. 11 is a flowchart of the member proposal process. As shown in FIG. 11, in the member proposal process, the proposal unit 42 determines whether or not an accessory is included in the members included in the product specification table 52 (S302). For example, the proposing unit 42 determines whether the member included in the product specification table 52 is an accessory based on the accessory flag of the member table 54. Specifically, when the accessory flag associated with the member included in the product specification table 52 is “1”, the proposing unit 42 determines that the member is an accessory. On the other hand, when the accessory flag associated with the member included in the product specification table 52 is “0”, the proposing unit 42 determines that the member is not an accessory.

  When determining that the accessory is included in the member of the product specification table 52 (S302: Yes), the proposing unit 42 determines whether the scheduled delivery date can be shortened by deleting the member that is an accessory. (S304). For example, when the inventory of the members that are accessories is less than the number requested by the customer, the proposing unit 42 determines that the scheduled delivery date can be shortened by omitting the members. On the other hand, when the inventory of the member that is an accessory is equal to or greater than the number requested by the customer, the proposing unit 42 determines that the scheduled delivery date cannot be shortened even if the member is omitted.

  If the proposal unit 42 determines that the scheduled delivery date can be shortened by deleting the accessory (S304: Yes), the proposal unit 42 generates a change proposal including the deletion of the accessory (S306), and executes the process of step S308. To do. If the proposing unit 42 determines that there is no accessory (S302: No), or determines that the scheduled delivery date cannot be shortened even if the accessory is deleted (S304: No), it executes the process of step S308.

  The proposing unit 42 includes members having the same basic configuration as the requesting member corresponding to the member determined to be included in the selection item in step S116 among the members included in the product specification table 52, but having different detailed configurations. It is determined with reference to the member table 54 (S308).

  When the proposing unit 42 refers to the member table 54 and determines that there is a member having the same basic configuration as the requested member included in the selection item but having a different detailed configuration (S308: Yes), the basic configuration is maintained. On the other hand, it is determined whether or not the planned delivery date can be shortened by changing to a member having a different detailed configuration (S310).

  When the proposing unit 42 determines that the scheduled delivery date can be shortened by changing the request member to a member having a different detailed configuration (S310: Yes), the proposal unit 42 generates a change proposal using the member having a different detailed configuration as the change member ( S312), the member proposal process is terminated. For example, the proposal unit 42 is different in the Nth detailed configuration (here, standard specification) for realizing 4 GB which is the basic configuration of the memory which is one of the required members, for example, the Nth detailed configuration is special. The member having the member ID “B005” as the specification may be used as the changing member. In addition, when the inventory of the member with the member ID “B005” does not satisfy the required number, the proposing unit 42 may use a member having a different high-level detailed configuration as a changed member. For example, the proposing unit 42 uses another member having a different first detailed configuration (here, two 2 GB) for realizing 4 GB which is the basic configuration of the memory, for example, the first detailed configuration is one 4 GB. A certain member ID “B007” may be used as a memory changing member.

  If the proposing unit 42 determines that there is no member having the same basic configuration as the member included in the selection item but a different detailed configuration (S308: No), or the planned delivery date even if the member is changed to a member having a different detailed configuration If it is determined that the process cannot be shortened (S310: No), the member proposal process is terminated.

  Returning to FIG. 9, when the proposing unit 42 determines that the selection item does not include a member (S116: No), it determines whether the selection item includes the number of units (S120). When the proposing unit 42 determines that the selection item includes the number of units (S120: Yes), the proposing unit 42 executes a unit number proposing process for generating a change proposal including the number of units that can be manufactured by the requested delivery date as the changed number of units (S122). ).

  FIG. 12 is a flowchart of the number proposal process. As shown in FIG. 12, in the number proposing process, the proposing unit 42 determines whether or not one or more products in the customer product specification table 52 can be manufactured by the requested delivery date (S402). For example, the proposing unit 42 searches the member table 54 for the inventory status of all the members included in the product specification table 52, and determines whether one or more units can be manufactured. Specifically, the proposing unit 42 determines that one or more units can be manufactured if the inventory of all the members included in the product specification table 52 is one or more. On the other hand, the proposing unit 42 determines that none of the members included in the product specification table 52 can be manufactured when there is no inventory of any member. The proposing unit 42 may determine whether one or more units can be manufactured based on the number of workers indicated by the work-in-progress information 64 or based on the number of workers and the inventory status.

  If the proposing unit 42 determines that no unit can be manufactured by the requested delivery date (S402: No), the number proposing process is terminated.

  When the proposing unit 42 determines that one or more units can be manufactured by the requested delivery date (S402: Yes), the proposing unit 42 calculates the number of units that can be manufactured by the requested delivery date (S404). The proposing unit 42 generates a change proposal including the calculated number of manufacturable units as the changed number (S406), and ends the number proposing process. Based on the inventory status and in-process information 64 in the member table 54, the proposing unit 42 generates a change proposal in which the number of units that can be manufactured by the requested delivery date on September 12 (for example, 20 units) is the changed number. Further, the proposing unit 42 may calculate and include a delivery date (for example, September 13) that can manufacture the remaining five units in the change proposal.

  When the proposing unit 42 determines that the selected item does not include the number of units (S120: No), the proposing unit 42 determines whether the selected item includes the cost (S124). When the proposal unit 42 determines that the selection item includes the cost (S124: Yes), the proposal unit 42 performs the cost proposal process of generating the change proposal including the additional cost for generating at least a part of the number of the vehicles by the requested delivery date as the change cost. Execute (S126).

  FIG. 13 is a flowchart of the cost proposal process. As shown in FIG. 13, in the cost proposal process, the proposal unit 42 determines whether one or more products can be manufactured by the requested delivery date (S502).

  When the proposing unit 42 determines that one or more products can be manufactured by the requested delivery date (S502: Yes), the proposing unit 42 calculates the number of units that can be manufactured at an additional cost by the requested delivery date (S504). The proposing unit 42 generates a change proposal including the changed number that can be manufactured at the additional cost and the additional cost as the changed cost (S506).

  If the proposing unit 42 determines that no product can be manufactured by the requested delivery date (S502: No), the proposing unit 42 calculates the shortage days that are insufficient for manufacturing one unit (S508). The proposing unit 42 calculates an additional cost necessary for the shortage days (S510). The proposing unit 42 generates a change proposal including the additional cost of the shortage days as the change cost (S512), and ends the cost proposing process.

  Returning to FIG. 9, when the proposing unit 42 determines that the selection item does not include an expense (S124: No), the proposing process is terminated. When the customer does not select the selection item and no change history exists in the change history table 60 as in the initial state, the selection item does not include any of the member, the number of units, and the cost. In such a case, the suggesting unit 42 determines in step S124 that the selected item does not include a cost.

  When executing any one of steps S118, S122, and S126, the proposing unit 42 determines whether all selection items have been processed (S128). The proposing unit 42 repeats step S116 and subsequent steps until all selection items are processed (S128: No).

  When all the selection items are processed (S128: Yes), the proposing unit 42 determines whether there is a change proposal generated in any one of steps S118, S122, and S126 (S130).

  When the proposal unit 42 determines that there is a change proposal (S130: Yes), the proposal unit 42 generates a proposed manufacturing plan 62 shown in FIG. 8 based on the generated one or more change proposals (S132). The proposal unit 42 transmits the generated change proposal and the proposed manufacturing plan 62 to the customer ordering apparatus 12 (S134), and ends the proposal process.

  When determining that there is no change proposal (S130: No), the proposing unit 42 generates a basic configuration change proposal for changing the basic configuration (S136). The proposal unit 42 transmits the generated basic configuration change proposal to the customer ordering apparatus 12 (S138), and ends the proposal process.

  FIG. 14 is a block diagram illustrating a hardware configuration of a computer 600 that functions as a part of the delivery date proposal device 14. As illustrated in FIG. 14, the computer 600 that functions as a part of the delivery date proposal device 14 includes a CPU 602, a ROM 604, a RAM 606, an HDD 608, an I / F 610, and a bus 612.

  The CPU 602 is an example of a hardware processor. The CPU 602 functions as the proposal-side control unit 30 by reading the proposal program 46 stored in the ROM 604.

  The ROM 604 stores programs such as firmware.

  The RAM 606 temporarily stores data necessary for execution of the program when the CPU 602 executes the program such as the proposal program 46.

  The HDD 608 stores programs such as the proposal program 46.

  The RAM 606 and the HDD 608 function as the proposal-side storage unit 32 during the execution of the proposal program 46.

  The I / F 610 connects an external device or the like to the CPU 602 or the like. For example, the I / F 610 connects the CPU 602 to the network 16 via the bus 612. The I / F 610 connects the CPU 602 to the proposal side display device 34 and the proposal side input device 36 via the bus 612.

  The computer functioning as the ordering apparatus 12 has the same hardware configuration as the computer 600 of FIG.

  As described above, in the delivery date proposal system 10, when the delivery date proposal device 14 does not satisfy the requested delivery date of the customer when the scheduled delivery date calculated from the requirement specification of the customer's product, the change proposal in which at least a part of the requested specification is changed. Generate and provide. Thereby, the delivery date proposal apparatus 14 can improve a customer's response, and can improve a customer's satisfaction.

  For example, the delivery date proposal device 14 generates and provides a change proposal in which a member of a product is changed to another member without changing the basic configuration of the product. Thereby, the delivery date proposal apparatus 14 can improve a customer's satisfaction, without changing the performance of a product.

  The delivery date proposal device 14 generates and provides a change proposal including a changed number indicating the number that can be manufactured by the requested delivery date among the requested number of customers. Thereby, the delivery date proposal apparatus 14 can tell a customer that at least a part can be manufactured by a requested delivery date, and can improve a customer's satisfaction.

  The delivery date proposal device 14 includes a change cost that indicates an additional cost for the number of units required by the customer to be manufactured by the requested delivery date or a change cost that indicates an additional cost for reducing the number of days that are insufficient to manufacture one unit. Proposals are generated and provided. Thereby, the delivery date proposal apparatus 14 can tell a customer the number etc. which can be manufactured by a requested delivery date by a change expense, and can improve a customer's satisfaction.

  Moreover, the delivery date proposal apparatus 14 provides the change proposal containing a some change content among a change member, the number of change, and a change expense according to a customer's selection item etc. Thereby, the delivery date proposal device 14 can provide a change proposal that brings the scheduled delivery date closer to the requested delivery date.

  The delivery date proposal device 14 sets a selection item based on the change history table 60 indicating the customer's past selection, and provides a change proposal with higher customer satisfaction even when the selection item cannot be acquired from the customer. it can.

  Although several embodiments of the present invention have been described, these embodiments are presented by way of example and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the scope of the invention. These embodiments and modifications thereof are included in the scope and gist of the invention, and are included in the invention described in the claims and the equivalents thereof.

DESCRIPTION OF SYMBOLS 10 ... Delivery date proposal system 14 ... Delivery date proposal apparatus 30 ... Proposal side control part 32 ... Proposal side memory | storage part 40 ... Determination part 42 ... Proposal part

Claims (6)

A determination unit that determines whether or not a planned delivery date calculated based on a requested member that is a member of a product requested by a customer and a requested number of products that is the number of the products satisfies a requested delivery date;
If the planned delivery date does not satisfy the required delivery date, a proposal unit that generates a change proposal that changes a customer's request to bring the planned delivery date closer to the requested delivery date;
A delivery date proposal device comprising: The proposal section
When the scheduled delivery date does not satisfy the required delivery date, a detailed configuration of the request member that realizes the basic configuration so as to bring the planned delivery date closer to the required delivery date while maintaining the basic configuration that is the configuration of the product. The delivery date proposal device according to claim 1, wherein the change proposal including the changed change member is generated. The proposal section
If the scheduled delivery date does not satisfy the requested delivery date, the change proposal including the changed number that is the number that can be manufactured by the requested delivery date is generated among the requested numbers so that the scheduled delivery date approaches the requested delivery date. The delivery date proposal device according to claim 1 or 2. The proposal section
The said change proposal including the change expense which changed the expense of the said product so that the said scheduled delivery date may be approximated to the said requested delivery date when the said scheduled delivery date does not satisfy | fill the said requested delivery date. The delivery date proposal device described in the section. If the proposed delivery date does not satisfy the required delivery date,
A change member that changes the detailed configuration of the request member that realizes the basic configuration so that the planned delivery date approaches the required delivery date while maintaining the basic configuration that is the configuration of the product,
Of the required number of units, the number of changed units that can be manufactured by the required delivery date, so as to bring the planned delivery date closer to the requested delivery date, and
Among the change costs for changing the cost of the product so as to bring the planned delivery date closer to the requested delivery date,
The delivery date proposal apparatus according to any one of claims 1 to 4, wherein the change proposal including a plurality of the change member, the number of changes, and the change cost is generated. The said proposal part produces | generates the said change proposal based on the change history which is the log | history of the said change proposal while producing | generating the said change proposal corresponding to the member, the number, or expense which the said customer selected. The delivery date suggestion device according to any one of the above.

Images