JP6641438B1 - Delivery request system and computer program used therefor - Google Patents

Abstract

An object of the present invention is to provide a delivery request system suitable for streamlining or streamlining the delivery of goods to a delivery destination provided with a vending machine. The present invention is applied to a physical distribution mode in which goods to be replenished to a vending machine (5) of a plurality of delivery destinations (DT) from a physical distribution base (2) via a distribution base (3) are distributed using a predetermined container (7). A delivery request including a server that provides delivery request information specifying the type and quantity of a product to be delivered from the base 2 to the delivery base 3 to the system 20 of the logistics company that is responsible for the distribution from the distribution base 2 to the delivery base 3 In the system, the server determines, for each delivery destination DT, the type and quantity of the product to be accommodated in each container 7 corresponding to the replenishment information indicating the replenishment quantity of the product for each delivery destination DT, and for each determined container 7 And generates the delivery request information that specifies the type and quantity of the product in association with the delivery destination information, and transmits the delivery request information to the system of the distribution company. [Selection] Figure 2

Description

  The present invention relates to a system and the like for requesting delivery of goods necessary for replenishing goods to a vending machine.

  In order to replenish products to vending machines, generally, a group of products is loaded on a delivery vehicle at a delivery base to which a certain area is assigned, and the vending machines are sequentially visited along a predetermined visiting route (delivery route). It is performed by a method in which goods are appropriately loaded and unloaded at each destination and necessary goods are supplied to the vending machine. In recent years, an attempt has been made to make the vending machine function as a network terminal by connecting the vending machine to a server via a network. In a system equipped with such a mechanism, information such as the sales performance of each vending machine is collected by the server, the replenishment quantity of the product of each vending machine is calculated, and according to the obtained replenishment quantity, a container for each vending machine is created. There has also been proposed a method of picking up products to reduce the time and effort of selecting products at a visiting place and to improve the efficiency of replenishment work (for example, see Patent Document 1).

JP 2013-61806 A

  In the system described in Patent Literature 1, picking work is performed at a delivery base serving as a base of a delivery route in each place. Therefore, delivery bases provided in each place have picking facilities and are sufficient and sufficient for picking. You need to keep a quantity of goods. The number of distribution bases is relatively large because vending machines in various places are provided in association with regions that can be visited within one day or within a shorter time. It may not always be appropriate to demand the burden of equipment and space from such a distribution base. On the other hand, the delivery of goods to distribution bases in various places generally takes place from large-scale shipping bases such as manufacturing bases and storage bases of goods, such as manufacturers and importers, who supply the goods to a relatively large area. Is usually performed hierarchically up to distribution bases in various places via distribution bases that cover the distribution. For such wide-area distribution, specialized logistics companies covering the whole country, such as home delivery companies, often have established a suitable mechanism. Therefore, if the resources of such traders can be effectively used, the efficiency of delivery can be improved as a whole. However, the delivery of a product to a delivery base is performed in units of packages of the same type of product created at the manufacturing base or the like. This is because the delivery request to the delivery base is made in accordance with the stock status of the delivery base, or in the upstream of the delivery base (closer to the manufacturing base or the like), the delivery route from the delivery base to the delivery route ahead of the delivery base. This is due to the fact that it is not possible to know the convenience of delivery, and as in the case of home delivery etc., there is no other choice but to deliver the product with the delivery base as the destination. Therefore, after all, it is necessary to open and pick the package at each delivery site.

  Therefore, an object of the present invention is to provide a delivery request system or the like suitable for streamlining or rationalizing the delivery of goods to a delivery destination provided with a vending machine.

A delivery request system (10) according to one aspect of the present invention provides a delivery request (DT) from a distribution base (2) storing a plurality of types of products (BP) to a plurality of delivery destinations (DT) via a delivery base (3). Goods are delivered, and at least one vending machine (5) for selling at least a part of the plurality of kinds of goods is installed at each of the plurality of delivery destinations, and from the distribution base to the delivery base. In each of the delivery and the delivery from the delivery base to the delivery destination, a standardized cargo handling body (7) is configured to be applied to a logistics form used as a unit of delivery, and is required at each delivery destination. The distribution request information (D3) specifying the type and quantity of commodities to be delivered from the distribution base to the distribution base in accordance with the replenishment quantity of each of the commodities described above is transmitted from the distribution base to the distribution base. Should carry A delivery request system including a server (11) as a computer provided to a system of a distributor (20) via a network (NT), wherein the server replenishes each product for each delivery destination. in response to designation of replenishment information indicating the quantity (D2), product type and quantity of goods to be handling each handling member according to handling limitations in the handling thereof, and to be delivered to different destinations Are determined for each of the delivery destinations so as not to be loaded on the same cargo handling body, and the determined product type and quantity of each cargo handling body are determined by unique delivery destination designation information (for example, FIG. Delivery request information generating means (33, S7, S8) for generating information specified in association with the customer code) as the delivery request information; Information transmitting means for transmitting the relative system (34, S9), is provided, said delivery request information generating unit, products to be handling into one handling member does not exceed the limit of the cargo body Allocating the goods to be delivered to the same delivery destination to one or more cargo handling units and executing the processing separately for each delivery destination, and determining the type and quantity of the goods to be delivered to one delivery destination. The delivery request information is generated by including, as a result of the assignment processing, a record associated with delivery destination designation information corresponding to a delivery destination and information indicating a difference in a cargo handling body assigned to each product. Is what you do.

A computer program (PG) according to one aspect of the present invention includes a computer program (PG) that stores a plurality of types of products (BP) from a distribution base (2) to a plurality of delivery destinations (DT) via a delivery base (3). Is delivered to each of the plurality of delivery destinations, at least one vending machine (5) that sells at least a part of the plurality of types of commodities is installed, and a delivery from the distribution base to the delivery base is performed. In each of the delivery and the delivery from the delivery base to the delivery destination, a delivery request system (10) configured to apply a standardized cargo handling body (7) to a logistics form used as a delivery unit is provided. The server (11) as a computer included includes a server for determining the type and quantity of goods to be delivered from the distribution base to the delivery base according to the replenishment quantity of each goods required at each delivery destination. For a delivery request system that functions to provide, via a network (NT), a delivery request information (D3) to be assigned to a distribution company system (20) that is responsible for distribution from the distribution base to the delivery base. The computer program according to any one of claims 1 to 3, wherein the server is configured to determine the type and quantity of goods to be unloaded by each cargo handling object in response to the specification of replenishment information (D2) indicating the replenishment quantity of each commodity for each of the delivery destinations . In accordance with the restrictions on cargo handling in each cargo handling body, the products to be delivered to different delivery destinations are determined for each delivery destination so as not to be mixed in the same cargo handling body. A delivery request that generates information for designating the quantity in association with delivery destination designation information unique to each delivery destination (for example, the customer code in FIG. 8) as the delivery request information. Information generating means (33, S7, S8), and the generated delivery request information, the information transmitting means for transmitting to said distributor system (34, S9), to function as the delivery request information generating unit The process of allocating goods to be delivered to the same delivery destination to one or more cargo handling bodies so that the goods to be handled by one cargo handling body does not exceed the limit of the cargo handling body is defined for each delivery destination. Separately, the type and quantity of goods to be delivered to one delivery destination are specified by the delivery destination designation information corresponding to the one delivery destination, and the information indicating the difference of the cargo assigned to each product. the records associated with the one in which as included as a result of the allocating process is configured so that to generate the delivery request information.

  According to the above aspect, the type and quantity of goods to be unloaded by each cargo handling object are determined for each delivery destination according to the restrictions of the cargo handling equipment, and the determined product type and quantity of each cargo handling object are determined by the delivery destination designation information. The delivery request information specified in association with the request is created, and the delivery request data is provided to the system of the distributor. Therefore, it is possible to load the goods into the cargo handling objects at the distribution base for each delivery destination and to deliver those cargo handling bodies to the delivery bases. In other words, it is possible to deliver the goods from the distribution base to the delivery base in a state where the goods are classified into the cargo handling units for each delivery destination according to the convenience of the delivery from the delivery base. Therefore, there is no need to carry out picking work at a delivery site that is responsible for final delivery of goods and replenishment of goods to the vending machine, and only loading the cargo corresponding to the delivery destination on the delivery vehicle etc. Delivery and replenishment operations can be performed. Alternatively, it is not necessary to take out a necessary quantity of commodities from the package for each commodities at the delivery destination and go to replenishment. Therefore, it is possible to streamline or streamline the work of delivering and replenishing the product to the delivery destination. Further, since there is no need to store a sufficient quantity of products for the picking operation at the delivery base, it is possible to save space to be secured at the delivery base.

  In one aspect of the present invention, the delivery request information generating means may generate the delivery request information so as to include information indicating the quantity of the cargo handling material used for each delivery destination. In this case, since the quantity of cargo handling equipment corresponding to each delivery destination is included in the delivery request information, at least the distribution base can grasp the total number of cargo handling equipment to be directed to each delivery destination. Therefore, at the time of loading / unloading of cargo at a distribution base, or at the time of loading / unloading of cargo at a distribution base, it is possible to easily and reliably confirm the number of cargo to be directed to the same destination. is there.

  In the physical distribution mode, a plurality of delivery routes (RT1, RT2) are set for one delivery base, and a plurality of delivery destinations corresponding to the one delivery base are classified into any of the plurality of delivery routes. The delivery request information generating means may generate the delivery request information so as to include information for specifying the delivery route. According to this, since information for distinguishing the delivery route is given to the distribution base, the distribution base can add the information indicating the delivery route and send the cargo to the delivery base. Thereby, the delivery base can easily and reliably determine which delivery route the cargo handling body should be directed to.

  The delivery request information generating means may generate the delivery request information by including information indicating the number of delivery destinations included in one delivery route. According to this, information indicating the number of delivery destinations is given to the distribution base, so that the distribution base adds information indicating how many delivery destinations are included in one delivery route, and The body can be sent to the delivery base. Therefore, at the time of loading / unloading of cargo at a distribution base, or at the time of loading / unloading of cargo at a distribution base, etc., it is possible to easily and surely check whether the cargo handling corresponding to all requested delivery destinations is present without omission. Can be determined.

  The vending machine at each delivery destination is connected to the server via the network, and the server acquires information (D1) necessary to determine the replenishment quantity of each product from each vending machine. Means (31, S1), and supplementary information generating means (32, S2 to S6) for generating the supplementary information based on information acquired from each vending machine, wherein the delivery request information generating means is The delivery request information may be generated based on the supplementary information generated by the supplementary information generating means. According to this, since the delivery request system also executes processing up to the generation of supplementary information, it is possible to streamline or streamline the work required to generate the delivery request information.

  In the above description, reference numerals in the accompanying drawings are added in parentheses to facilitate understanding of the present invention, but the present invention is not limited to the illustrated embodiment.

The figure showing the outline of the physical distribution form to which the delivery request system concerning one form of the present invention is applied. The figure which shows the example of delivery of the drink from a distribution base to each delivery destination via a delivery base. The figure which shows the outline of the work procedure performed in order to deliver a drink from a distribution base to a delivery base. The figure showing an example of the composition of the server in an operation system. 5 is a flowchart illustrating an example of a procedure of a delivery request process executed by the server in FIG. 4. The figure which shows an example of the result data of FIG. The figure which shows an example of the replenishment plan data of FIG. The figure which shows an example of the picking request data of FIG. The figure which shows an example of the slip issued by the physical distribution system side.

  First, an example of a distribution form to which a delivery request system according to an embodiment of the present invention is applied will be described with reference to FIG. In the logistics form illustrated in FIG. 1, a beverage BP (see FIG. 2) as an example of a product is transferred from a shipping base 1 such as a manufacturing factory 1 </ b> A or a storage warehouse 1 </ b> B of a manufacturer to a distribution base 3 via the distribution base 2. Will be delivered. The delivery to the distribution base 2 is performed in a state where the beverage BP is packed in a package PK such as a carton by type. A freight vehicle 4 or the like may be appropriately used for the delivery.

  The delivery base 3 has a designated area. The delivery base 3 is a base for delivering a product with the vending machine 5 installed in the area in charge as a delivery destination DT. In the delivery base 3, a delivery route is set. FIG. 1 shows an example in which two delivery routes RT1 and RT2 (hereinafter, may be represented by RT) are set in one delivery base 3, but at least one delivery route 3 is set for one delivery base 3. It is sufficient that one delivery route RT is set. When a plurality of delivery routes RT are set for one delivery site 3, the vending machines 5 existing in the area in charge of the delivery site 3 are appropriately classified into any of the delivery routes RT. The worker at the delivery base 3 loads the goods on the delivery vehicle 6, sequentially visits the vending machines 5 according to the delivery route RT, and replenishes the vending machines 5 with the goods. The area in charge of the delivery base 3 is set to a range that allows the patrol of the vending machine 5 within one day or less. The distribution base 2 is provided so as to cover a wider area than the distribution area of the delivery base 3. Although only one distribution base 2 is shown in FIG. 1, a plurality of distribution bases 2 may be provided in different areas. The plurality of distribution bases 2 may be provided hierarchically so as to narrow the area in charge. Alternatively, the beverage BP may be relayed between a plurality of distribution bases 2 in different areas.

  FIG. 2 illustrates an example of delivery from one distribution base 2 to one delivery base 3 and delivery from the delivery base 3 along one delivery route RT. For delivery from the distribution base 2 to the delivery base 3 and delivery from the delivery base 3 to the vending machine 5 of the delivery destination DT, a container 7 as an example of a cargo handling body is used. That is, the delivery from the distribution base 2 to the delivery destination DT via the delivery base 3 is performed on a container 7 basis. The container 7 is configured as a foldable rectangular parallelepiped container as an example. The size and shape of the container 7 are standardized. A plurality of types of standards may exist for the container 7, and in that case, a container 7 of a standard suitable for delivery of the beverage BP may be appropriately selected. The container 7 has certain restrictions on cargo handling. As an example, each container 7 has a limit on the weight that can be stored. However, the restriction does not necessarily need to be set as an absolute upper limit. A limit may be set as a guide to allow a slight excess. The limitation on the cargo handling of the container 7 is not limited to the example based on the weight. Instead of or in addition to the weight, the total volume, length, and the like of the beverage BP may be set as restrictions.

  The picking of the beverage BP into the container 7 is performed at the distribution base 2 for each delivery destination DT. The number of containers 7 used for one delivery destination DT changes according to the number of beverages BP to be delivered to the delivery destination DT. In other words, while a plurality of containers 7 may be used for one delivery destination DT, beverages BP destined for different delivery destinations DT are not mixedly loaded in the same container 7. The container 7 in which the beverage BP is unloaded at the distribution base 2 is delivered to the delivery base 3 in charge of the delivery destination DT to which the beverage BP in the container 7 is to be delivered. The container 7 delivered to the delivery base 3 is sequentially delivered to the delivery destination DT according to the schedule of the visit to the delivery destination DT of the delivery base 3, and the beverage BP stored in the container 7 is refilled in the vending machine 5. . As described above, in the present embodiment, instead of opening the package PK at the delivery base 3 and performing the picking operation for each delivery destination DT, the work is performed on the upstream side of the delivery base 3, that is, the manufacturing factory 1A and the storage warehouse 1B. The picking work is performed at the distribution base 2 located on the side closer to the shipping base 1 by distinguishing the containers 7 for each delivery destination DT.

  FIG. 2 shows an example in which one vending machine 5 is installed at one delivery destination DT, but the delivery destination DT is a unit in which the work of loading and unloading goods from the delivery vehicle 6 and replenishing is performed. One delivery destination DT may include a plurality of vending machines 5. The vending machine 5 does not necessarily need to be able to sell all types of beverages BP that can be delivered from the distribution base 2, and it is sufficient that at least some types of beverages BP can be sold. The number of delivery destinations DT included in one delivery route RT may be appropriately changed. In the case where the beverage BP is sequentially delivered between a plurality of distribution bases 2 provided in a hierarchical manner, or when the beverage BP is delivered while being relayed between a plurality of distribution bases 2 in different areas, one of the distributions Picking to the container 7 is performed at the base 2. The delivery by the package PK is performed on the upstream side of the distribution base 2 where the picking is performed, and the delivery by the container 7 is performed on the downstream side. Delivery from the delivery base 3 is performed periodically, for example, once a day. However, it is not always necessary that all delivery destinations DT are set as delivery targets in each delivery. Every time the delivery is performed, the delivery destination DT in the delivery route RT may be appropriately selected. The delivery route RT may be appropriately changed according to the convenience of delivery. The delivery may be performed such that a plurality of delivery vehicles 6 share the delivery destination DT in one delivery route RT.

  Returning to FIG. 1, the description will be continued. The delivery from the shipping base 1 to the distribution base 2 and the delivery from the distribution base 2 to the distribution base 3 are distribution operations for a relatively large area, while the delivery from the distribution base 3 to the distribution destination DT is In addition to delivery within a relatively small area with a limited range, operation management such as replenishment of beverages BP to individual vending machines 5, collection of sales proceeds of vending machines 5, maintenance of vending machines 5 It is a business that includes. Therefore, the former business is in charge of, for example, a company constructing a nationwide logistics network, and the latter business is in charge of a company that operates and manages the individual vending machines 5. The subject may be divided. In the following, the trader in charge of the logistics business up to the delivery base 3 is referred to as a distributor, and the trader in charge of the delivery from the distribution base 3 and the replenishment of beverages BP is referred to as an operator. However, the logistics company and the operating company do not necessarily need to be mutually independent companies, and may be companies having capital relationships such as affiliated companies and subsidiaries. The point is that they are distinguished according to the scope of work in charge of the distribution company and the operator. Accordingly, the distribution base 3 may be a distribution branch of a distribution company or a store such as a distribution center set up by an operator. The delivery from the delivery base 3 and the replenishment of the beverage BP may also be realized by the business entity of the delivery base 3 or a company entrusted by the person.

  Each of the distributor and the operator usually builds an information processing system in order to carry out its own business. FIG. 1 illustrates an information processing system operated by an operator as an operating system 10 and an information processing system of a distributor as a distribution system 20. The operation system 10 includes a server 11 connected to vending machines 5 in various places via a network NT, and a terminal device 12 as a client for the server 11. The distribution system 20 similarly includes a server 21 and a terminal device 22 as a client for the server 21. The distribution system 20 is further provided with a client such as a printer 23 for printing out a picking instruction slip or the like at the distribution base 2. Various clients may also be provided in the operation system 10, but are not shown in FIG. The delivery base 3 may also be provided with a client appropriately connected to the servers 11 and 21.

  The operation system 10 functions as an example of a delivery request system that requests a distribution company to deliver to the delivery base 3. The server 11 of the operation system 10 determines the type and quantity of the beverage BP to be replenished to each vending machine 5 based on the information collected from the vending machine 5, and delivers it to the server 21 of the distribution system 20 according to the result. Provide data to request. At the distribution base 2, the picking content for the container 7 for each delivery destination DT is determined based on the data provided from the operation system 10, and the beverage BP is picked according to the determination result.

  Next, with reference to FIG. 3, an outline of an operation procedure performed for delivering the beverage BP from the distribution base 2 to the delivery base 3 will be described. Although the operation in FIG. 3 may be repeatedly performed at an appropriate cycle, it is assumed here that the operation is repeated once a day. In the following, a procedure for one delivery site 3 is taken as an example, but the operation of FIG. 3 may be performed for each of the plurality of delivery sites 3. First, in the operation system 10, performance data is collected from the vending machines 5 in various places (F11). The performance data is information necessary for determining the quantity of the beverage BP to be refilled in each vending machine 5. A specific example will be described later. The collection of the result data may be performed by determining the execution time in association with the delivery date and time of the delivery from the delivery base 3, for example, the night before the day when the delivery from the delivery base 3 is to be performed.

  Next, the management system 10 creates a replenishment plan for each delivery route RT corresponding to the delivery base 3 based on the information collected from the vending machine 5 (F12). In the replenishment plan, a vending machine of a delivery destination DT to be visited among delivery destinations DT included in the delivery route RT and a delivery destination DT to be visited (hereinafter, this may be referred to as a destination). 5 is a visit plan that defines the content of replenishment of the beverage BP with respect to No. 5, for example, the type and quantity (number) of the beverage BP to be replenished. Thereafter, the management system 10 creates picking request data as an example of delivery request information to a distributor based on the replenishment plan (F13). Details of the procedure for creating the picking request data will be described later. The created picking request data is provided to the distribution system 20 (F14).

  In the distribution system 20, picking request data is obtained (F21), and a slip is created based on the obtained picking request data (F22). The slip is created for each container 7 and printed out at the distribution base 2 as appropriate. Each slip includes information on the contents of the picking operation and the delivery base 3 and the delivery destination DT to which the container 7 is to be delivered. Since one container 7 corresponds to one delivery destination DT, the picking content of the beverage BP to be delivered to each of the plurality of delivery destinations DT is not described in one slip. A specific example of the slip will be described later. Subsequently, the distribution company performs a picking operation to store the beverage BP stored in the distribution base 2 in the container 7 according to the instruction of the slip (F23). When the picking operation corresponding to the picking request data is completed, each container 7 containing the beverage BP is delivered to the delivery base 3 (F24).

  At the delivery site 3, the containers 7 delivered from the distribution site 2 are temporarily stored, and each container 7 is loaded on the delivery vehicle 6 with the start of delivery preparation (F31). Thereafter, the delivery vehicle 6 starts visiting the delivery destinations DT as destinations, and the vending machines 5 of the delivery destinations DT are sequentially refilled with the beverage BP (F32). In this case, since the containers 7 are distinguished for each delivery destination DT, it is sufficient for the workers at each delivery destination DT to load and unload only the container 7 corresponding to the delivery destination DT. Therefore, the replenishment work at the visited place is made more efficient.

  Of the work procedures shown in FIG. 3, procedures F11 to F14 in the operation system 10 are performed as processing of the server 11 in the operation system 10. FIG. 4 shows an example of the configuration of the server 11 for implementing such processing. In the example of FIG. 4, the server 11 is configured as an example of a computer that operates according to a predetermined computer program PG. The server 11 can access the customer database DB1, the product database DB2, and the achievement database DB3 to read or write various data.

  The customer database DB1 is a database in which various types of information regarding the customer are recorded. The customer is another name of the delivery destination DT, and one delivery destination DT corresponds to one customer. As an example, the customer database DB1 holds a group of records in which various kinds of information about the customer, such as a customer name, a delivery route, and a visit schedule, are recorded in association with a unique customer code for each customer. The delivery route is information for specifying which delivery route RT of which delivery base 3 the customer is included in. The visit schedule is information that specifies when to visit a customer. For example, contents to be visited daily or on a specific day of every week are recorded as a visit schedule. The details of the vending machine 5 installed at the customer, for example, information indicating the model of the vending machine 5 and the number of columns may be further recorded in the customer database DB1.

  The product database DB2 holds a group of records in which various types of information on the beverage BP are recorded in association with a unique product code for each beverage BP. The information on the beverage BP includes, for example, product attributes such as a product name, a product capacity, and a weight. The data obtained at any time by the operation system 10 such as various data collected by the server 11 from the vending machine 5 or data of a replenishment plan created by the server 11 based on the data is stored in the performance database DB3. Stored. For example, data such as the sales record of the beverage BP in each vending machine 5 or the replenishment record of the beverage BP for each vending machine 5 is recorded in the record database DB3.

  The server 11 includes a data collection unit 31, a replenishment plan creation unit 32, a picking request data creation unit 33, and a data transmission unit 34 as logical devices realized by a combination of the computer hardware of the server 11 and the computer program PG. Provided. The data collection unit 31 collects various types of information from each vending machine 5, and records the obtained information as a result data D1 in a storage device (not shown) of the server 11. The information collected by the data collection unit 31 includes information to be referred to in creating a supplementary plan, and the information is stored in the performance data D1.

  The replenishment plan creating unit 32 creates (generates) a replenishment plan based on the performance data D1, and records the obtained replenishment plan in the replenishment plan data D2. In creating a replenishment plan, the replenishment plan creating unit 32 appropriately refers to the customer database DB1, the product database DB2, or the performance database DB3. The picking request data creating unit 33 creates (generates) picking request data D3 based on the replenishment plan data D2. In creating the picking request data D3, the picking request data creating unit 33 appropriately refers to the customer database DB1, the product database DB2, or the performance database DB3. The data transmission unit 34 transmits the picking request data D3 to the server 21 of the distribution system 20 at an appropriate timing. The performance data D1, replenishment plan data D2, and picking request data D3 created by the server 11 are appropriately recorded in the performance database DB3 as needed.

  FIG. 5 shows an example of a procedure of a delivery request process realized by cooperation of the units 31 to 34 of the server 11. The process of FIG. 5 is a specific example of a process executed by the server 11 to implement the work procedures F11 to F14 illustrated in FIG. 3, and illustrates a process corresponding to one delivery route RT. The delivery request processing in FIG. 5 is executed at a predetermined time to request the physical distribution system 20 for picking. When the processing in FIG. 5 is started, first, the data collection unit 31 collects information necessary for creating a replenishment plan from each vending machine 5, and records this in the performance data D1 (step S1). Next, the replenishment plan creation unit 32 refers to the visit schedule in the customer database DB1 and determines a delivery destination DT to be selected as the next visit from the delivery destinations DT in the delivery route RT (step S2). At the time of selecting a visit destination, information of each vending machine 5 recorded in the performance data D1, for example, information such as the stock amount of each beverage BP is referred to, and the delivery destination DT of the vending machine 5 that does not need replenishment is referred to. May be excluded.

  Subsequently, the supplementary plan creation unit 32 selects any one of the visits selected in step S2 as a processing target (step S3). Thereafter, the replenishment plan creating unit 32 refers to the information recorded in the performance data D1 regarding the vending machine 5 of the visited site selected as the processing target, and refers to the information on the beverage BP to be replenished in the vending machine 5. Are determined as replenishment contents (step S4). When determining the replenishment content, the replenishment plan creating unit 32 may predict the replenishment quantity with reference to the sales performance or the replenishment performance information recorded in the performance database DB3. In determining the visit destination in step S2 and determining the supplement content in step S4, the visit destination or supplement content may be appropriately modified based on an instruction of the operator of the terminal device 12 of the operation system 10.

  When the replenishment content for one visit is determined, the replenishment plan creating unit 32 determines whether or not the processing in steps S3 and S4 has been completed for all the visits selected in step S2, and If there is, the process returns to step S3. When the processing has been completed for all the visits, the supplementary plan creating unit 32 creates supplementary plan data D2 recording the supplementary contents for each visit determined in the current process, and stores this in the storage device of the server 11 ( Step S6).

  When the replenishment plan D2 is saved, the processing shifts to the creation of the picking request data D3 by the picking request data creation unit 33. The picking request data creation unit 33 first reads the replenishment plan data D2, and allocates a container 7 for each visit based on the replenishment content for each visit (step S7). In this case, the beverage BP to be delivered to each destination is allocated to one or more containers 7 so that the total weight of the beverage BP allocated to one container 7 does not exceed the limit weight of the container 7. . Since the processing in step S7 is performed separately for each visit, the beverage BP to be delivered to a plurality of visits is not assigned to one container 7.

  When the assignment to the container 7 is completed, the picking request data creation unit 33 creates the picking request data D3 based on the replenishment plan data D2 and the assignment result to the container 7, and stores this in the storage device of the server 11 ( Step S8). Thereafter, the data transmission unit 34 transmits the picking request data D3 to the server 21 (FIG. 1) of the distribution system 20 at a predetermined timing (step S9). When the data transmission is completed, the server 11 ends the current delivery request processing.

  Next, specific examples of the data D1 to D3 created by the server 11 will be described with reference to FIGS. FIG. 6 shows an example of the performance data D1. 6 is data obtained by recording information acquired from the vending machine 5 in association with a unique customer code for each customer (delivery destination DT). FIG. 6 shows an example of data relating to the vending machine 5 corresponding to each of the customer codes 1005, 1024, 1031 and 1041, but the numerical values and the like are virtual and do not necessarily reflect actual examples. It does not do. In the example of FIG. 6, as the information acquired from the vending machine 5, the column, the product code, the actual number, the full number, and the stock number are included in the actual data D1. The column indicates the position of the storage column of the beverage BP included in one vending machine 5, and a unique number is assigned to each column. For example, the vending machine 5 of the customer code 1005 has columns 1 to C1. The product code is a code indicating the beverage BP contained in each column, and corresponds to the product code used in the product database DB2 in FIG. The actual results are the quantity of beverage BP sold between the previous information collection and this information collection, the full number is the maximum number of beverage BPs in each column, and the inventory is the beverage BP at the time of information collection. The remaining number. The measurement date, that is, the date when the information was acquired from the vending machine 5, is also recorded in the performance data D1. Part of the information recorded in the performance data D1 is obtained from the customer database DB1 or the product database DB2, or based on information obtained from the vending machine 5 and information recorded in the databases DB1 and DB2. May be created. For example, the full information may be calculated based on the model information of the vending machine 5 recorded in the customer database DB1 and the product attributes recorded in the product database DB2. The product code of the beverage BP contained in each column may be set on the vending machine 5 side, for example, or may be managed on the server 11 side.

  FIG. 7 shows an example of replenishment plan data D2 created corresponding to the performance data D1 shown in FIG. In the example of FIG. 7, each of the customers recorded in the performance data D1 is selected as a visitor, and a column, a delivery route, a product code, and a replenishment quantity are recorded in association with the customer code of the visitor. ing. The delivery route is specified by a unique code for each delivery route RT, for example. As an example, the code of the delivery route is recorded in the customer database DB1 in association with the customer code, and is obtained by searching the customer database DB1 using the customer code as a key. The replenishment quantity is appropriately determined based on the sales performance quantity, the full quantity, and the stock quantity in the performance data D1. By referring to the sales result or the replenishment result recorded in the result database DB3, the vending machine 5 stores the quantity of the beverage BP such that the beverage BP is not sold out within the visit interval of the visit destination. A replenishment quantity may be determined. That is, the replenishment quantity does not necessarily need to be determined as a quantity necessary for filling each column of the vending machine 5 with the beverage BP.

  FIG. 8 shows an example of picking request data D3 created corresponding to the replenishment plan data D2 shown in FIG. In the example of FIG. 8, as the information for specifying the contents of the picking request corresponding to each of the delivery destinations DT, information on the product code, the indicated quantity, the delivery base, the eaves number, the eaves serial number, and the route number is used as the visit destination. It is recorded in association with the customer code of the selected delivery destination DT. The designated quantity is the quantity of the beverage BP to be picked into one container 7, and is the quantity allocated to one container 7 in step S7 of FIG. Because the same beverage BP may be allocated to two or more containers 7 in relation to the weight limit of the container 7, the value of the indicated quantity may be smaller than the replenishment quantity in FIG. For example, in the replenishment plan data D2 in FIG. 7, it is determined that the delivery destination DT indicated by the customer 1005 should be refilled with 23 beverages BP indicated by the product code 3527. On the other hand, in the picking request data D3 of FIG. 8, as is clear from the portion indicated as “container division”, two records corresponding to the product code 3527 exist, and the indicated quantities are 2 and 21, respectively. Have been. This indicates that the replenishment quantity of the beverage BP of the product code 3527 should be divided and picked so that one container 7 has two bottles and the other container 7 has 21 bottles. For the product code 3527 of the customer 1031 as well, the designated quantity is specified separately for the two containers 7.

  The information of the delivery base indicates the delivery base 3 to which the container 7 is to be delivered. That is, the information on the delivery base is used as information indicating the destination of the container 7 from the distribution base 2 where the picking operation is performed. In the example of FIG. 8, either "branch" or "center" is designated. For example, “branch” indicates a specific delivery base 3 operated by an operator, and “center” indicates a specific delivery base 3 operated by a distributor. However, when there are many delivery bases 3, a unique base code may be set for each delivery base 3 and the base code may be designated as the information of the delivery base.

  The house number is information for distinguishing between customers (delivery destinations DT). As an example, an eaves number is set from the first record of the picking request data D3 so as to be a 5-digit serial number for each customer code. In the example of FIG. 8, the eaves number 00001 is set for the delivery destination DT of the customer code 1005, and the eaves number 00002 is set for the delivery destination DT of the next customer code 1024. Similarly, the customer code changes in the same manner. A serial number is assigned to each of them as an eaves number. The eaves number is set to be a serial number regardless of the difference of the delivery base. Therefore, the maximum value of the eaves destination number of the picking request data D3 is a value indicating the number of delivery destinations DT specified by the picking request data D3. Since the number of delivery destinations DT can be ascertained from the picking request data D3, for example, at the distribution base 2, it is necessary to determine how many containers 7 of the delivery destination DT exist at the time of picking work or loading of the containers 7. It is possible to easily and surely confirm. The same applies when unloading the container 7 at the delivery base 3, which is effective in preventing leakage of the delivery destination DT.

  The eaves serial number is N / M, where N is the number when the containers 7 corresponding to the same eaves number are sequentially numbered from 1, and M is the total number of containers 7 corresponding to the same eaves number. It is set as follows. For example, when a total of p1 containers 7 are used for the eaves number 00001 in FIG. 8, eaves serial numbers are set for each container 7, such as 1 / p1, 2, p1... P1 / p1. Therefore, when the numerator portions (serial number portions) of the eaves serial numbers match, the beverages BP for which the eaves serial numbers are designated are stored in the same container 7. If the eaves number is different, the eaves serial number is set again from 1 again. By referring to the eaves serial number, it is possible to grasp how many containers 7 exist in total for the destination DT indicated by the same eaves number, in other words, the destination DT indicated by the same customer code. It is possible to Therefore, for example, at the distribution base 2, it is possible to easily and surely confirm how many containers 7 exist for the same delivery destination DT at the time of the picking operation or the loading of the containers 7. . The same applies when unloading containers 7 at the delivery base 3, and furthermore, by referring to the information, it is possible to easily and surely confirm how many containers 7 exist at each delivery destination DT. For this reason, it is effective in preventing some of the containers 7 from being forgotten to be stacked or leaking from being unloaded.

  The route number is information indicating the difference between the delivery routes RT and the number of delivery destinations DT included in the same delivery route RT. In the example of FIG. 8, a four-digit numerical value is set as the route number. In the first two digits of the route number, the last two digits of the delivery code set in the delivery route RT corresponding to the delivery destination DT are set. For example, since the code of the delivery route corresponding to the customer code 1005 in FIG. 7 is 1061, the first two digits of the route number corresponding to the customer code 1005 in the picking request data D3 in FIG. On the other hand, the last two digits of the route number in the picking request data D3 are set so as to be serial numbers sequentially from 1 for each delivery destination DT having a common delivery route RT. In the example of FIG. 7, when it is assumed that there are a total of XY delivery destinations DT corresponding to the delivery route 1061 (that is, the first two digits of the route number are 61), the picking request data D3 in FIG. The last two digits of the corresponding route number are serial numbers from 1 to XY for each customer code. Therefore, by referring to the last two digits of the route number, it is possible to grasp the number of delivery destinations DT (visit destinations) included in the same delivery route. By providing the information on the delivery route to the distribution base 2, the container 7 can be sent to the delivery base 3 with the information indicating the delivery route added. Thus, the delivery base 3 can easily and reliably determine which delivery route RT the container 7 is to be directed to.

  The picking request data D3 created as described above is appropriately converted into a format suitable for data communication and transmitted to the server 21 of the distribution system 20. In the distribution system 20, the beverage BP is picked according to the picking request data D3 acquired by the server 21. Since the picking request data D3 specifies the product code and the quantity of the beverage BP to be accommodated for each container 7, the picking work is performed according to the specification, so that the vending machines 5 in various places should be refilled. The beverage BP is stored in the container 7 separately for each delivery destination DT. The specific procedure of the picking operation may be appropriately determined by the distributor, but as an example, a slip 50 as shown in FIG. 9 is printed out for each container 7 based on the picking request data D3, and the slip 50 is It may be provided to the picking process as attached to the container 7.

  In the slip 50 in FIG. 9, the destination part 51 indicating the delivery base described in the picking request data D3, the customer code and the name thereof (obtained from the customer database DB1 and included in the picking request data D3 can be specified. ), An eaves number, an eaves designation part 53 showing the eaves serial number and the route number, and a display part 54 showing the name and number (quantity) of the beverages BP stored in the container 7. Is provided. Further, when it is necessary to read various information corresponding to the picking request data D3 by the optical reading means, the slip 50 may be provided with an identification image 55 such as a barcode in which the various information is embedded. . However, the details of the slip 50 are not limited to the example of FIG. 9 and can be changed as appropriate. In short, the slip 50 is attached to the container 7 and delivered to the delivery base 3, so that the record of the picking request data D3 corresponds to the container 7 or the container to be delivered to which delivery destination DT. 7 is sufficient if it can be identified. When an electronic storage medium such as an RFID tag is attached to the container 7, the slip 50 may be recorded on the storage medium as electronic data. Regarding the information to be recorded on the slip 50, for example, even if the customer code and the customer name are omitted and only the eaves number is displayed, if the picking request data D3 can be browsed at the delivery base 3, It is possible to determine to which delivery destination DT each container 7 should be delivered using the eaves number as a key.

  As described above, according to the operation system 10 of the present embodiment, the type and quantity of the beverage BP to be accommodated in each container 7 are determined for each delivery destination DT according to the weight limitation of the container 7, and are determined. Because the picking request data D3 in which the type and quantity of the beverage BP for each container 7 is specified in association with a unique customer code for each delivery destination DT is created, and the data D3 is transmitted to the distribution system 20. In the distribution base 2, the beverage BP can be picked into the container 7 separately for each delivery destination DT, and the container 7 can be delivered to the delivery base 3. Therefore, it is not necessary to carry out picking work at the delivery base 3 which is a base responsible for delivery and replenishment along the delivery route RT, and the container 7 corresponding to the visit included in the delivery route RT is transferred to the delivery vehicle 6. Delivery and replenishment can be performed simply by loading. Alternatively, it is not necessary to take out a necessary number of beverages BP from the package PK for each beverage BP at the delivery destination DT and go to replenishment. Therefore, the work of delivering and replenishing the beverage BP to the delivery destination DT can be made more efficient. In addition, since it is not necessary to store a sufficient number of beverages BP necessary and necessary for the picking operation at the delivery base 3, the space to be secured at the delivery base 3 can be reduced.

  In the above embodiment, the picking request data creating unit 33 of the server 11 executes the processing of steps S7 and S8 in FIG. 5 to function as an example of a delivery request information generating unit. By executing the processing in step S9, the function as an example of the information transmitting means is achieved. Further, the data collection unit 31 of the server 11 executes the processing of step S1 in FIG. 5 to function as an example of an information acquisition unit, and the supplementary plan creation unit 32 executes the processing of steps S2 to S6 in FIG. Functions as an example of supplementary information generating means. Further, the picking request data D3 shown in FIG. 8 corresponds to an example of delivery request information, and the supplement plan data D2 shown in FIG. 7 corresponds to an example of supplement information. The customer code in the picking request data D3 corresponds to an example of delivery destination specification information, the information of the product code and the indicated quantity corresponds to information specifying the type and quantity of the product, and the first two digits of the route number indicate the delivery route. The last two digits correspond to the information indicating the number of delivery destinations, the serial number on the numerator side in the eaves serial number corresponds to the information indicating the quantity of cargo, and the last two digits correspond to the eaves serial number. The numerical value on the denominator side corresponds to information indicating the number of cargo handling bodies.

  The present invention is not limited to the above embodiment, and may be embodied in embodiments in which various modifications or changes are made. For example, in the above embodiment, the server 11 collects information from the vending machine 5 and creates a replenishment plan based on the obtained information as a part of the delivery request processing in FIG. The acquisition of information from the vending machine 5 and the creation of a replenishment plan are performed by another system or the like, and the data of the created replenishment plan is provided to the server 11 to perform the processing from step S7 in FIG. The delivery request system may be configured so that the server 11 is in charge.

  In the above embodiment, the picking request data D3 includes the information for specifying the delivery route. However, when only one delivery route is set for one delivery base, or when the delivery base sets the delivery route according to the situation. When it is not necessary to distinguish the delivery routes as in the case where the delivery route is appropriately changed, or when there is a situation where the delivery route is not determined, the delivery request information does not need to include the information specifying the delivery route. Even in this case, since the picking request data D3 includes the customer code specifying the delivery destination, it is possible to determine which container 7 is to be delivered to which delivery destination DT using the customer code as a key. It is possible. Further, the information indicating the number of destinations DT or the information indicating the quantity of containers 7 corresponding to the same destination DT is used when the containers 7 are loaded at the distribution base 2 or when the containers 7 are stored at the distribution base 3. When loading / unloading, it is effective to confirm the quantity of containers 7 directed to each delivery destination DT or to prevent leakage of the delivery destination DT itself. Further, it is also effective in loading the containers 7 at the delivery base 3 or for convenience in unloading the containers 7 at the delivery destination DT. However, even without such information, as long as it is possible to specify which container 7 corresponds to which delivery destination DT, the container 7 can be specified for each delivery destination DT and correctly delivered.

  The goods targeted by the delivery request system of the present invention are not limited to beverages BP, but may be various kinds of goods that can be sold by vending machines. The cargo handling body used for delivery of the goods is not limited to the foldable container 7, and various types of packages, containers, pedestals, carts, and the like that can be used for cargo handling may be used as the cargo handling body.

DESCRIPTION OF SYMBOLS 1 Shipping base 1A Manufacturing factory 1B Storage warehouse 2 Distribution base 3 Delivery base 5 Vending machine 7 Container (handling body)
10 Management system (delivery request system)
11 server 20 distribution system 21 server 31 data collection unit (information acquisition means)
32 Replenishment plan creation part (replenishment information generation means)
33 Picking request data creation unit (delivery request information generation means)
34 Picking request data transmission unit (information transmission means)

Claims (6)

The goods are delivered to each of a plurality of delivery destinations from a distribution base storing a plurality of kinds of goods via a delivery base, and at least a part of the plurality of kinds of goods is sold to each of the plurality of delivery destinations. At least one vending machine is installed, and in each of delivery from the distribution base to the delivery base and delivery from the delivery base to the destination, a standardized cargo handling unit is used as a unit of delivery. Delivery that is configured to be applied to a distribution form to be delivered and that specifies the type and quantity of goods to be delivered from the distribution base to the delivery base according to the replenishment quantity of each product required at each delivery destination. A delivery request including a server as a computer that provides request information via a network to a system of a logistics company that is responsible for logistics from the distribution base to the distribution base. A stem,
In the server,
In response to the specification of the replenishment information indicating the replenishment quantity of each product for each delivery destination, the type and quantity of the product to be unloaded by each cargo handling unit are set to different delivery destinations according to the restriction of the cargo handling in each cargo handling unit. Is determined for each of the delivery destinations so that the goods to be delivered to the same cargo carrier are not mixed, and the type and quantity of the product for each of the determined cargo carriers is uniquely specified for each delivery destination. Delivery request information generating means for generating information designated in association with the delivery request information, and information transmitting means for transmitting the generated delivery request information to the system of the distributor .
The delivery request information generating means allocates the goods to be delivered to the same delivery destination to one or a plurality of cargo handling bodies so that the goods to be handled by one handling body do not exceed the limit of the cargo handling bodies. The process is executed separately for each destination, and the type and quantity of the product to be delivered to one destination is specified by the delivery destination designation information corresponding to the one destination and the cargo handling assigned to each product. A delivery request system that generates the delivery request information by including, as a result of the assigning process, a record associated with information indicating a physical difference .   2. The delivery request system according to claim 1, wherein the delivery request information generating unit generates the delivery request information by including information indicating a quantity of the cargo body used for each delivery destination. 3. In the physical distribution mode, a plurality of delivery routes are set for one delivery base, and a plurality of delivery destinations corresponding to the one delivery base are classified into any of the plurality of delivery routes,
The delivery request system according to claim 1, wherein the delivery request information generating unit generates the delivery request information by including information for specifying the delivery route.   4. The delivery request system according to claim 3, wherein the delivery request information generating means generates the delivery request information by including information indicating the number of delivery destinations included in one delivery route. A vending machine at each delivery destination is connected to the server via the network,
In the server,
Information acquisition means for acquiring information necessary for determining the replenishment quantity of each product from each vending machine, and replenishment information generation means for generating the replenishment information based on information acquired from each vending machine,
Is further provided,
The delivery request system according to any one of claims 1 to 4, wherein the delivery request information generating unit generates the delivery request information based on the supplementary information generated by the supplementary information generating unit. The goods are delivered to each of a plurality of delivery destinations from a distribution base storing a plurality of kinds of goods via a delivery base, and at least a part of the plurality of kinds of goods is sold to each of the plurality of delivery destinations. At least one vending machine is installed, and in each of delivery from the distribution base to the delivery base and delivery from the delivery base to the destination, a standardized cargo handling unit is used as a unit of delivery. A server as a computer included in a delivery request system configured to be applied to a given distribution form is distributed from the distribution base to the delivery base according to the replenishment quantity of each product required at each delivery destination. Delivery request information specifying the type and quantity of goods to be provided is sent to a network of a logistics company that is responsible for logistics from the distribution base to the distribution base. A computer program for a delivery request system to function as a file,
Said server,
In response to the specification of the replenishment information indicating the replenishment quantity of each product for each delivery destination, the type and quantity of the product to be unloaded by each cargo handling unit are set to different delivery destinations according to the restriction of the cargo handling in each cargo handling unit. Is determined for each of the delivery destinations so that the goods to be delivered to the same cargo carrier are not mixed, and the type and quantity of the product for each of the determined cargo carriers is uniquely specified for each delivery destination. A delivery request information generating means for generating information to be specified in association with the delivery request information, and an information transmitting means for transmitting the generated delivery request information to the system of the distributor .
The delivery request information generating means allocates the goods to be delivered to the same delivery destination to one or a plurality of cargo handling bodies so that the goods to be handled by one handling body do not exceed the limit of the cargo handling bodies. The process is executed separately for each destination, and the type and quantity of the product to be delivered to one destination is specified by the delivery destination designation information corresponding to the one destination and the cargo handling assigned to each product. A computer program for a delivery request system configured to generate the delivery request information by including, as a result of the assigning process, a record associated with information indicating a physical difference .

Images