Delivery date management device, delivery date management method, and delivery date management program

Abstract

To provide a delivery date management device, a delivery date management method, and a delivery date management program that enable assistance for delivery date control on delivery by visualizing to which site and when delivery is to be performed / has been performed and how many times delivery to the same site is to be performed / has been performed based on a shipping schedule and shipping result.SOLUTION: Order receipt data in which a delivery destination, a scheduled shipping date, and a delivery date have been set is acquired. A proposal target delivery schedule which is a delivery schedule to be targeted for a proposal for a change of the date of shipping to the delivery destination is specified based on the order receipt data. Delivery detail data in which the scheduled date of shipping to the delivery destination, the number of shipping to the delivery destination, and the presence / absence of the proposal target delivery schedule have been set is acquired, and a delivery schedule screen including the delivery detail data is displayed.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present invention relates to a delivery date management device, a delivery date management method, and a delivery date management program. [Background technology]

[0002] Patent Document 1 discloses a configuration for managing delivery dates so that construction materials are delivered to a construction site on a specified date based on the determination of date information written in an information member attached to the construction materials. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 08-028054 Summary of the Invention [Problem to be solved by the invention]

[0004] However, the invention described in the above Patent Document 1 has a problem in that it is not possible to improve profits by suppressing logistics costs through delivery date control.

[0005] The present invention has been made in consideration of the above problems, and aims to provide a delivery date management device, a delivery date management method, and a delivery date management program that can assist in controlling delivery dates by visualizing when delivery will be made / has been made to which site, and how many deliveries are planned / has been made to the same site, based on shipping schedules (backlogs) and shipping records. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the delivery date management device of the present invention is a delivery date management device equipped with a memory unit and a control unit, and the control unit is characterized in that it comprises: an order acquisition means for acquiring order data setting a delivery destination, a scheduled shipping date, and a delivery date; a delivery acquisition means for identifying a proposed target delivery schedule, which is a delivery schedule that is the subject of a proposed shipping date change to the delivery destination based on the order data, and acquiring delivery detail data setting the scheduled shipping date to the delivery destination, the number of shipments to the delivery destination, and whether or not the proposed target delivery schedule exists; and a delivery schedule display means for displaying a delivery schedule screen including the delivery detail data.

[0007] In addition, in the delivery date management device of the present invention, the delivery acquisition means identifies the delivery schedule that results in shipment to the delivery destination on consecutive days as the proposed delivery schedule based on the order data, and acquires the delivery detail data that sets the scheduled shipping date to the delivery destination, the number of shipments to the delivery destination, and the presence or absence of the proposed delivery schedule.

[0008] In addition, in the delivery date management device of the present invention, the order data further includes settings for the construction period, type of work, and size of the delivery destination, and the delivery schedule display means further specifies the appropriate number of shipments to the delivery destination and whether or not there is available space based on the order data, and displays a delivery date negotiation proposal screen including site data setting the construction period, type of work, appropriate number of shipments, and whether or not there is available space.

[0009] In addition, in the delivery date management device of the present invention, the control unit further includes a weather acquisition means for acquiring weather data including a weather forecast for the delivery destination, and the delivery schedule display means identifies the appropriate number of shipments for the delivery destination and the presence or absence of available space based on the order data, and displays the delivery date negotiation proposal screen including the site data and the weather data.

[0010] In addition, in the delivery date management device of the present invention, the memory unit is equipped with a transaction memory means for storing shipping data setting the delivery destination and the shipping date, and the delivery acquisition means identifies the proposed delivery schedule to the delivery destination based on the order data and the shipping data, and acquires the delivery detail data including schedule detail data setting the planned shipping date to the delivery destination, the number of shipments to the delivery destination, and the presence or absence of the proposed delivery schedule, as well as actual detail data setting the shipping date to the delivery destination and the number of shipments to the delivery destination.

[0011] In addition, in the delivery date management device according to the present invention, the delivery acquisition means further acquires, based on the order data and the shipping data, delivery data that includes the actual number of shipments to the delivery destination, the scheduled number of shipments to the delivery destination, the shipping number which is the sum of the actual number of shipments and the scheduled number of shipments, and whether or not there is a delivery schedule to be proposed.

[0012] In addition, in the delivery date management device of the present invention, the delivery data is characterized in that it has set therein the previous actual shipping count, which is the number of actual shipping attempts at the time the order data was last obtained, the previous scheduled shipping count, which is the number of scheduled shipping attempts at the time the order data was obtained, the previous shipping count, which is the number of shipments at the time the order data was obtained, and previous presence / absence, which is the presence or absence of the proposed delivery schedule at the time the order data was obtained.

[0013] In addition, in the delivery date management device of the present invention, the delivery schedule display means displays an extraction screen that allows the user to select the delivery detail data to be displayed depending on the presence or absence of the proposed delivery schedule, and displays the delivery schedule screen including the delivery detail data to be displayed based on the selection instruction on the extraction screen.

[0014] In addition, in the delivery date management device of the present invention, the control unit is further characterized by having an order modification means for displaying an order input screen which enables the scheduled shipping date set in the order data to be changed to a revised scheduled shipping date, and acquiring updated order data in which the scheduled shipping date set in the order data has been changed to the revised scheduled shipping date based on a change instruction inputted on the order input screen.

[0015] In addition, the delivery date management method of the present invention is a delivery date management method to be executed by a delivery date management device equipped with a memory unit and a control unit, and is characterized by including an order acquisition step to be executed by the control unit, which acquires order data setting a delivery destination, a scheduled shipping date, and a delivery date; a delivery acquisition step to identify a proposed target delivery schedule, which is a delivery schedule that is the subject of a proposed shipping date change change to the delivery destination based on the order data, and acquire delivery detail data setting the scheduled shipping date to the delivery destination, the number of shipments to the delivery destination, and whether or not there is a proposed target delivery schedule; and a delivery schedule display step to display a delivery schedule screen including the delivery detail data.

[0016] In addition, the delivery date management program of the present invention is a delivery date management program to be executed by a delivery date management device having a memory unit and a control unit, and is characterized in that the control unit executes an order acquisition step of acquiring order data setting a delivery destination, a scheduled shipping date, and a delivery date, a delivery acquisition step of identifying a proposed delivery schedule, which is a delivery schedule that is the subject of a proposed shipping date change change to the delivery destination based on the order data, and acquiring delivery detail data setting the scheduled shipping date to the delivery destination, the number of shipments to the delivery destination, and whether or not there is a proposed delivery schedule, and a delivery schedule display step of displaying a delivery schedule screen including the delivery detail data. Effect of the Invention

[0017] The present invention has the effect of supporting delivery date control to the same site. Also, the present invention has the effect of improving the efficiency of delivery route determination in transportation operations, thereby realizing reduction in logistics costs. Also, the present invention has the effect of enabling delivery date adjustment by visualizing logistics costs in cases where shipments are made to the same delivery destination periodically, thereby enabling measures to be taken to reduce logistics costs such as delivery costs. Also, the present invention has the effect of enabling index information to be created to reduce the number of shipments based on the shipping history, and appropriate shipping number management and alerts according to the characteristics of the site. [Brief description of the drawings]

[0018] [Figure 1] FIG. 1 is a diagram showing an example of delivery date management processing in this embodiment. [Diagram 2] FIG. 2 is a block diagram showing an example of the configuration of the delivery date management device according to this embodiment. [Diagram 3] FIG. 3 is a flowchart showing an example of a process of the delivery date management device in this embodiment. [Figure 4] FIG. 4 is a diagram showing an example of delivery date management processing in this embodiment. [Diagram 5] FIG. 5 is a diagram showing an example of delivery date management processing in this embodiment. [Figure 6] FIG. 6 is a diagram showing an example of delivery date management processing in this embodiment. [Figure 7] FIG. 7 is a diagram showing an example of delivery date management processing in this embodiment. [Figure 8] FIG. 8 is a diagram showing an example of delivery date management processing in this embodiment. [Figure 9] FIG. 9 is a diagram showing an example of delivery date management processing in this embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0019] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described in detail with reference to the drawings. However, the present invention is not limited to the embodiment.

[0020] [1. Overview] First, an overview of the present invention will be described with reference to Fig. 1. Fig. 1 is a diagram showing an example of delivery date management processing in this embodiment.

[0021] In the building materials industry, there are many cases where the volume of goods is large and deliveries are often made to the same site multiple times, so logistics costs often put pressure on profits. Therefore, if sales representatives can negotiate with site supervisors and control delivery dates (arrangements) to ship materials together, logistics costs can be reduced as a result. However, traditionally, construction sites have been the ones to ship building materials when the site supervisors told them they needed them, which resulted in a lot of unnecessary shipping, such as daily shipments to the same site (delivery destination).

[0022] Therefore, in this embodiment, focusing on the tendency for wasteful deliveries (such as multiple deliveries to the same site) to increase and the resulting increase in logistics costs, a system is provided that controls delivery dates to reduce logistics costs and improve profits. That is, in this embodiment, based on the shipping schedule (backlog) and shipping performance, it is calculated when and how many deliveries are planned to be made to which site, or have actually been made, and based on the calculation results, it is possible to grasp the daily shipments and number of shipments to each site.

[0023] For example, as shown in FIG. 1, in this embodiment, delivery data is created based on the shipping schedule (order data) and shipping results (shipping data), and based on the created delivery data, the delivery schedule and results table makes it possible to check which site to ship to and when, as well as the number of shipments. If there is a possibility of shipments on consecutive days, the person in charge is made to negotiate the delivery date with the site, and if the delivery date negotiations are successful, the shipping date is changed when the order is entered.

[0024] [2. Configuration] An example of the configuration of the delivery date management device 100 according to this embodiment will be described with reference to Fig. 2. Fig. 2 is a block diagram showing an example of the configuration of the delivery date management device 100 according to this embodiment.

[0025] 2, the delivery date management device 100 is a commercially available desktop personal computer. Note that the delivery date management device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may be a portable information processing device such as a commercially available notebook personal computer, a PDA (Personal Digital Assistant), a smartphone, or a tablet personal computer.

[0026] The delivery date management device 100 comprises a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. The units included in the delivery date management device 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0027] The communication interface unit 104 communicably connects the delivery date management device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via the communication line. Here, the network 300 has a function of connecting the delivery date management device 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network).

[0028] An input device 112 and an output device 114 are connected to the input / output interface unit 108. The output device 114 may be a monitor (including a touch panel), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that cooperates with a mouse to realize a pointing device function. In the following, the output device 114 may be referred to as the monitor 114 or the printer 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

[0029] The storage unit 106 stores various databases, tables, files, etc. The storage unit 106 records computer programs for cooperating with an OS (Operating System) to give instructions to a CPU (Central Processing Unit) to perform various processes. For example, memory devices such as RAM (Random Access Memory) and ROM (Read Only Memory), fixed disk devices such as hard disks, flexible disks, and optical disks can be used as the storage unit 106. The storage unit 106 includes a transaction database 106a.

[0030] The transaction database 106a stores transaction data. Here, the transaction database 106a may store shipping data in which a delivery destination and a shipping date are set. The transaction data may also include order data, delivery details data, site data, weather data, schedule details data, actual details data, and delivery data.

[0031] The control unit 102 is a CPU or the like that performs overall control of the delivery date management device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, required data, etc., and executes various information processing based on these stored programs. The control unit 102 conceptually includes an order acquisition unit 102a, a delivery acquisition unit 102b, a weather acquisition unit 102c, a delivery schedule display unit 102d, and an order correction unit 102e.

[0032] The order acquisition unit 102a acquires order data. Here, the order acquisition unit 102a may acquire order data in which a delivery destination, a scheduled shipping date, and a delivery date are set. Here, the order data may include a construction period, a construction type, and / or a scale of the delivery destination. In addition, the order acquisition unit 102a may register the order data in the transaction database 106a.

[0033] The delivery acquisition unit 102b acquires delivery statement data that sets the presence or absence of a proposed delivery schedule, which is a delivery schedule that is a target for a proposed change in shipping date to the delivery destination. Here, the delivery acquisition unit 102b may identify a proposed delivery schedule, which is a delivery schedule that is a target for a proposed change in shipping date to the delivery destination, based on the order data, and acquire delivery statement data that sets the scheduled shipping date to the delivery destination, the number of shipments to the delivery destination, and the presence or absence of the proposed delivery schedule. Also, the delivery acquisition unit 102b may identify a delivery schedule that involves shipping to the delivery destination every day as a proposed delivery schedule, based on the order data, and acquire delivery statement data that sets the scheduled shipping date to the delivery destination, the number of shipments to the delivery destination, and the presence or absence of the proposed delivery schedule. The delivery acquisition unit 102b may also identify a proposed delivery schedule to the delivery destination based on the order data and the shipping data, and acquire delivery detail data including schedule detail data that sets the scheduled shipping date to the delivery destination, the number of shipments to the delivery destination, and the presence or absence of a proposed delivery schedule, and actual detail data that sets the shipping date to the delivery destination and the number of shipments to the delivery destination. The delivery acquisition unit 102b may also acquire delivery data that sets the actual number of shipments to the delivery destination, the scheduled number of shipments to the delivery destination, the number of shipments that is the sum of the actual number of shipments and the scheduled number of shipments, and the presence or absence of a proposed delivery schedule based on the order data and the shipping data. Here, the delivery data may be set to the previous actual number of shipments, which is the actual number of shipments at the time of the previous order data acquisition, the previous scheduled number of shipments, which is the scheduled number of shipments at the time of the order data acquisition, the previous number of shipments, which is the number of shipments at the time of the order data acquisition, and the previous presence or absence, which is the presence or absence of a proposed delivery schedule at the time of the order data acquisition. Furthermore, the delivery acquisition unit 102b may register the delivery detail data and / or the delivery data in the transaction database 106a.

[0034] The weather acquisition unit 102c acquires weather data. Here, the weather acquisition unit 102c may acquire weather data including a weather forecast for the delivery destination. The weather acquisition unit 102c may also acquire weather data from a weather data providing service (for example, a weather data portal site or a weather data distribution company, etc.) via the network 300. The weather acquisition unit 102c may also register the weather data in the transaction database 106a.

[0035] The delivery schedule display unit 102d displays the delivery schedule. Here, the delivery schedule display unit 102d may display a delivery schedule screen including delivery detail data. The delivery schedule display unit 102d may specify the appropriate number of shipments to the delivery destination and the presence or absence of free space based on the order data, and display a delivery date negotiation proposal screen including site data that sets the construction period, construction type, appropriate number of shipments, and the presence or absence of free space. The delivery schedule display unit 102d may specify the appropriate number of shipments to the delivery destination and the presence or absence of free space based on the order data, and display a delivery date negotiation proposal screen including the site data and weather data. The delivery schedule display unit 102d may display an extraction screen that allows the user to select delivery detail data to be displayed depending on the presence or absence of a proposed delivery schedule, and may display a delivery schedule screen including the delivery detail data to be displayed based on a selection instruction on the extraction screen. The delivery schedule screen may include delivery data.

[0036] The order correction unit 102e corrects the order data. Here, the order correction unit 102e may display an order input screen that allows the scheduled shipping date set in the order data to be changed to the corrected scheduled shipping date, and may acquire updated order data in which the scheduled shipping date set in the order data has been changed to the corrected scheduled shipping date based on a change instruction inputted on the order input screen.

[0037] [3. Specific Examples] A specific example of this embodiment will be described with reference to FIGS.

[0038] [Delivery date management processing] An example of delivery date management processing in this embodiment will now be described with reference to Fig. 3. Fig. 3 is a flowchart showing an example of processing by the delivery date management device 100 in this embodiment.

[0039] As shown in FIG. 3, when the user inputs order items via the input device 112, the order acquisition unit 102a acquires order data including the delivery destination, scheduled shipping date, delivery date, construction period, type of work, and size of the delivery destination, and registers the order data in the transaction database 106a (step SA-1).

[0040] Then, based on the order data and shipping data stored in the transaction database 106a, the delivery acquisition unit 102b identifies a proposed delivery schedule, which is a delivery schedule that is the subject of a proposed change in shipping date to the delivery destination, acquires delivery detail data including schedule detail data that sets the scheduled shipping date to the delivery destination, the number of shipments to the delivery destination, and whether or not there is a proposed delivery schedule, and actual detail data that sets the shipping date to the delivery destination and the number of shipments to the delivery destination, and acquires delivery data that sets the actual number of shipments to the delivery destination, the scheduled number of shipments to the delivery destination, the number of shipments which is the sum of the actual number of shipments and the scheduled number of shipments, and whether or not there is a proposed delivery schedule (step SA-2).

[0041] Then, the weather acquisition unit 102c acquires weather data including a weather forecast for the delivery destination (step SA-3).

[0042] Then, the delivery schedule display unit 102d identifies the appropriate number of shipments to the delivery destination and whether or not there is available space based on the order data, and displays on the output device 114 a delivery schedule screen including delivery detail data, site data setting out the construction period, construction type, appropriate number of shipments to the delivery destination and whether or not there is available space, and a delivery date negotiation proposal screen including weather data (step SA-4).

[0043] Then, the order correction unit 102e displays on the output device 114 an order input screen that allows the scheduled shipping date set in the order data to be changed to the corrected scheduled shipping date, and determines whether or not a change instruction has been input to the order input screen via the input device 112 by the user (step SA-5).

[0044] If the order correction unit 102e determines that no change instruction has been input to the order input screen (step SA-5: No), the order correction unit 102e ends the process.

[0045] On the other hand, if the order correction unit 102e determines that a change instruction has been input to the order input screen (step SA-5: Yes), it shifts the process to step SA-6.

[0046] Then, based on the change instruction, the order correction unit 102e obtains updated order data in which the scheduled shipping date set in the order data stored in the transaction database 106a has been changed to the revised scheduled shipping date, and registers the updated order data in the transaction database 106a (step SA-6).

[0047] Then, based on the order data before the update, the order data after the update, and the shipping data stored in the transaction database 106a, the delivery acquisition unit 102b identifies a proposed delivery schedule, which is a delivery schedule that is the subject of a proposed shipping date change to the delivery destination, and acquires delivery detail data including schedule detail data setting the scheduled shipping date to the delivery destination, the number of shipments to the delivery destination, and whether or not there is a proposed delivery schedule, and actual detail data setting the shipping date to the delivery destination and the number of shipments to the delivery destination, and acquires delivery data setting the actual number of shipments to the delivery destination, the scheduled number of shipments to the delivery destination, the number of shipments which is the sum of the actual number of shipments and the scheduled number of shipments, whether or not there is a proposed delivery schedule, the previous actual number of shipments which is the actual number of shipments at the time the order data before the update was acquired, the previous scheduled number of shipments which is the scheduled number of shipments at the time the order data before the update was acquired, the previous number of shipments which is the number of shipments at the time the order data before the update was acquired, and previous presence / absence which is the presence or absence of a proposed delivery schedule at the time the order data before the update was acquired (step SA-7).

[0048] Then, the delivery schedule display unit 102d displays a delivery schedule screen including the delivery detail data and the delivery data on the output device 114 (step SA-8), and ends the process.

[0049] An example of delivery date management processing in this embodiment will now be described with reference to Fig. 4 to Fig. 9. Fig. 4 to Fig. 9 are diagrams showing an example of delivery date management processing in this embodiment.

[0050] In this embodiment, as shown in Fig. 4, when the user registers the order (scheduled shipping) data on the order input screen, and as shown in Fig. 5, when the execute button is pressed on the delivery data creation screen, delivery data in which the history SEQ, site code, site name, current shipping count (1), current shipping count (2), current shipping count (3), current consecutive shipping or not, previous shipping count (1), previous shipping count (2), previous shipping count (3), and previous consecutive shipping or not are set are created based on the order (scheduled shipping) data and shipping data, and delivery detail data in which the history SEQ, site code, site name, forecast / actual classification, shipping date, shipping count, and consecutive shipping or not are set are created. Here, the number of shipments (2) is the number of items (shipping performance up to now) tallied by the site code and shipping date of the shipping data, the number of shipments (3) is the number of items (ordered shipping schedule) tallied by the site code and shipping date of the order data, and the number of shipments (1) may be "number of shipments (2) + number of shipments (3)". In addition, in this embodiment, consecutive day shipments refer to cases where the shipping dates are consecutive business days. For example, if 1 / 30 and 1 / 31 are holidays, shipments on 1 / 28 and 2 / 1 may be determined to be consecutive day shipments.

[0051] In this embodiment, as shown in FIG. 6, a delivery schedule and performance table screen and a delivery date negotiation proposal screen are displayed based on the delivery data and delivery detail data. In this embodiment, the user can view this form screen and control the delivery date as necessary. In this embodiment, when extracting these form data, the user may be able to set the narrowing down based on the presence or absence of consecutive day shipments for each site on the extraction screen. In addition, in this embodiment, if the user determines the appropriate number of shipments for each construction period and type of construction and determines that the value is abnormal based on the site size, etc., the user may be allowed to input an instruction to consolidate the shipping date into 2 / 3. In addition, in this embodiment, the user is provided with a form screen that provides information for determining whether the current number of shipments is more than the appropriate number, information for negotiating delivery dates with the site to reduce the number of shipments based on site data and weather data if the current number of shipments is more than the appropriate number, and information for negotiating delivery dates with the site to reduce the number of shipments based on site data and weather data if consecutive day shipments are present.

[0052] In this embodiment, when the delivery date negotiation between the user and the site is successful and the order is entered in the correction mode, the shipping date and delivery date are changed as shown in Fig. 7. Here, as shown in Fig. 7, in this embodiment, the shipping date of the record in row number: 3 of the order data is changed to 2012 / 2 / 3, so that the order is not shipped on consecutive days.

[0053] In this embodiment, when the execute button is pressed on the delivery data creation screen, the data is recreated based on the changed order (shipment schedule) data, as shown in Fig. 8. In this embodiment, the history SEQ of the delivery data and delivery detail data is changed to distinguish them from before the update.

[0054] In this embodiment, a delivery schedule and results table screen is displayed so that the results of the delivery date adjustment can be confirmed based on the delivery data and delivery detail data, as shown in Fig. 9. In this manner, in this embodiment, as shown in Fig. 9, it can be confirmed that there are no more daily shipments to the site for which the delivery date adjustment was made this time, and that the number of shipments has been reduced.

[0055] [4. Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby contributing to goals 8 and 9 of the SDGs.

[0056] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of goals 12, 13, and 15 of the SDGs.

[0057] Furthermore, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

[0058] 5. Other embodiments The present invention may be embodied in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

[0059] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using known methods.

[0060] In addition, the processing procedures, control procedures, specific names, registered data for each process, information including parameters such as search conditions, screen examples, and database configurations shown in this specification and drawings may be changed as desired unless otherwise specified.

[0061] Moreover, with regard to delivery date management device 100, the components shown in the figures are merely conceptual functional elements, and the device does not necessarily have to be physically configured as shown in the figures.

[0062] For example, the processing functions of the delivery date management device 100, particularly the processing functions performed by the control unit 102, may be realized in whole or in part by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded in a non-transient computer-readable recording medium that includes programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the delivery date management device 100 as necessary. That is, a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). This computer program is executed by being loaded into a RAM, and cooperates with the CPU to form the control unit.

[0063] In addition, this computer program may be stored in an application program server connected to delivery date management device 100 via any network, and it is also possible to download all or part of it as necessary.

[0064] In addition, the program for executing the process described in this embodiment may be stored in a non-transient computer-readable recording medium, or may be configured as a program product. Here, the "recording medium" includes any "portable physical medium" such as a memory card, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable and Programmable Read Only Memory (EEPROM (registered trademark)), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray (registered trademark) Disc.

[0065] Moreover, a "program" is a data processing method written in any language or description method, and may be in any form, such as source code or binary code. Note that a "program" is not necessarily limited to a single configuration, but also includes a configuration that is distributed as a plurality of modules or libraries, and a program that achieves its function by cooperating with a separate program, such as an OS. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in this embodiment, as well as the installation procedure after reading, may use well-known configurations and procedures.

[0066] The various databases etc. stored in the memory unit 106 are storage means such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files etc. used for various processes and providing websites.

[0067] Furthermore, the delivery date management device 100 may be configured as an information processing device such as a known personal computer or a workstation, or may be configured as the information processing device to which any peripheral device is connected. Furthermore, the delivery date management device 100 may be realized by installing software (including programs or data, etc.) that causes the device to realize the processing described in this embodiment.

[0068] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be functionally or physically distributed and integrated in any unit according to various additions or functional loads. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively. [Industrial Applicability]

[0069] The present invention is useful in industries such as the steel industry, the building material industry, the trading industry, and the wholesale industry. [Explanation of symbols]

[0070] 100 Delivery date management device 102 Control section 102a Order Acquisition Department 102b Delivery Acquisition Department 102c Weather acquisition part 102d Delivery schedule display section 102e Order Adjustment Department 104 Communication interface section 106 Storage section 106a Trade Database 108 Input / Output Interface Section 112 Input Devices 114 Output Device 200 Servers 300 Network

Claims

1. A delivery date management device including a storage unit and a control unit, The control unit is an order acquisition means for acquiring order data including a delivery destination, a scheduled shipping date, and a delivery date; a delivery acquisition means for identifying a delivery schedule for which shipments are to be made every day to the delivery destination based on the order data as a proposed delivery schedule, and acquiring delivery detail data that sets the scheduled shipping date to the delivery destination, the number of shipments to the delivery destination, and whether or not there is the proposed delivery schedule; a delivery schedule display means for displaying a delivery schedule screen including the delivery detail data; A delivery date management device comprising:

2. The storage unit is a transaction storage means for storing shipping data in which the delivery destination and the shipping date are set; Equipped with The delivery acquisition means includes:

2. The delivery date management device according to claim 1, characterized in that, based on the order data and the shipping data, the delivery schedule in which shipments are made to the delivery destination on consecutive days is identified as the proposed delivery schedule, and the delivery detail data including schedule detail data setting the planned shipping date to the delivery destination, the number of shipments to the delivery destination, and whether or not the proposed delivery schedule exists, and actual detail data setting the shipping date to the delivery destination and the number of shipments to the delivery destination are acquired.

3. The delivery acquisition means includes: The delivery date management device according to claim 2, further comprising: based on the order data and the shipping data, a delivery data setting that includes a number of actual shipments to the delivery destination, a number of scheduled shipments to the delivery destination, the number of shipments which is the sum of the number of actual shipments and the number of scheduled shipments, and whether or not there is a delivery schedule to be proposed.

4. The delivery data is The delivery date management device according to claim 3, characterized in that the previous actual shipping count, which is the number of actual shipping attempts at the time the previous order data was obtained, the previous scheduled shipping count, which is the number of scheduled shipping attempts at the time the order data was obtained, the previous shipping count, which is the number of shipments at the time the order data was obtained, and previous presence / absence, which is the presence or absence of the proposed delivery schedule at the time the order data was obtained, are set.

5. The delivery schedule display means includes: The delivery date management device according to claim 1, further comprising: an extraction screen for selecting the delivery detail data to be displayed based on the presence or absence of the proposed delivery schedule; and a delivery schedule screen including the delivery detail data to be displayed based on a selection instruction on the extraction screen.

6. The control unit is an order modification means for displaying an order input screen that enables the scheduled shipping date set in the order data to be changed to a revised scheduled shipping date, and acquiring updated order data in which the scheduled shipping date set in the order data has been changed to the revised scheduled shipping date based on a modification instruction input on the order input screen; 6. The delivery date management device according to claim 1, further comprising:

7. A delivery date management method to be executed by a delivery date management device having a storage unit and a control unit, Executed in the control unit, an order acquisition step for acquiring order data including a delivery destination, a scheduled shipping date, and a delivery date; a delivery acquisition step of identifying a delivery schedule for which shipments are to be made every day to the delivery destination as a proposed delivery schedule based on the order data, and acquiring delivery detail data that sets the scheduled shipping date to the delivery destination, the number of shipments to the delivery destination, and whether or not there is the proposed delivery schedule; a delivery schedule display step of displaying a delivery schedule screen including the delivery detail data; A delivery date management method comprising:

8. A delivery date management program to be executed by a delivery date management device having a storage unit and a control unit, In the control unit, an order acquisition step for acquiring order data including a delivery destination, a scheduled shipping date, and a delivery date; a delivery acquisition step of identifying a delivery schedule for which shipments are to be made every day to the delivery destination as a proposed delivery schedule based on the order data, and acquiring delivery detail data that sets the scheduled shipping date to the delivery destination, the number of shipments to the delivery destination, and whether or not there is the proposed delivery schedule; a delivery schedule display step of displaying a delivery schedule screen including the delivery detail data; A delivery date management program to execute the above.

Images