Shipping Servers and How to Control Them

Abstract

To provide a shipping server and a shipping server control method which can improve convenience for a constructor being a client.SOLUTION: A shipping server 100 comprises work notification means. The work notification means includes: first work start notification means which, when client data does not include any shipping history, gives such a notification that work of shipping a solution and an injector for spraying the solution to a shipping destination is to be started; and second work start notification means which, when the client data includes a shipping history, gives such a notification that work of shipping the solution to the shipping destination but not shipping the injector to the shipping destination is to be started, at timing based on a scheduled shipping date calculated on the basis of the latest shipping date in the shipping history of the client data and a shipping interval in the client data. The shipping server 100 further includes: first expiration date notification means which notifies a contact address of an expiration date of the solution before the expiration date of the solution; and second time limit notification means which notifies the contact address of a re-execution time limit before a re-execution time limit which is a time limit to perform re-execution after performing the execution.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present invention relates to a shipping server and a shipping server control method, and more particularly to a shipping server and a shipping server control method for managing the shipping of a solution containing a photocatalyst to a customer. [Background technology]

[0002] Photocatalysts such as titanium oxide are known as substances that exhibit catalytic action when irradiated with light. Photocatalysts are known as substances that absorb light and exhibit catalytic action. When light hits a photocatalyst, it can cause chemical reactions at room temperature that are difficult to carry out using normal catalytic processes. By promoting oxidation-reduction reactions using photocatalysts, organic matter and bacteria are decomposed. For this reason, photocatalysts are used for sterilization and air purification, etc.

[0003] Conventional technology related to photocatalysts is disclosed, for example, in Patent Document 1 below. Patent Document 1 below discloses a spray product that includes a dispersion medium containing water, photocatalytic fine particles dispersed in the dispersion medium, a photocatalytic coating agent containing silver ions, and a sprayer that is configured to spray the photocatalytic coating agent. The concentration of silver ions in the photocatalytic coating agent is 0.6 ppm or more. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent Publication No. 2021-137706 Summary of the Invention [Problem to be solved by the invention]

[0005] The act of spraying a photocatalyst solution, which is a solution containing a photocatalyst, onto an object using a sprayer is called application. When the photocatalyst is applied, the solvent in the photocatalyst solution evaporates, leaving the photocatalyst on the surface of the object. This achieves the effect of photocatalyst application, which is to disinfect the surface of the object.

[0006] On the other hand, the disinfecting performance of a photocatalytic solution declines due to the proliferation of airborne bacteria that have become mixed into the solution, or due to deterioration caused by light or temperature. For this reason, photocatalytic solutions have an expiration date. To obtain sufficient disinfecting performance from a photocatalytic solution, the installer who applies the photocatalyst must remember the expiration date of the photocatalytic solution and remember to apply it before the expiration date. This reduces convenience for the installer.

[0007] In addition, because the photocatalyst has weak adhesion to the surface of an object, it peels off from the surface of the object due to contact with human hands or the passage of time, weakening the effectiveness of the photocatalyst application. Therefore, in order to maintain the effectiveness of the photocatalyst application, the applicator had to reapply the photocatalyst before the application effect weakened. The applicator had to remember when the application effect of the photocatalyst weakened, and remember to purchase the photocatalyst solution and sprayer and apply the photocatalyst again before the effect weakened. This resulted in low convenience for the applicator.

[0008] The present invention has been made to solve the above-mentioned problems, and its object is to provide a shipping server and a shipping server control method that can improve convenience for builders who are customers. [Means for solving the problem]

[0009] A shipping server according to one aspect of the present invention is a shipping server that manages shipping of a solution containing a photocatalyst to a customer, and includes: storage means for storing customer data, which is data relating to the customer, including at least the customer's contact information, a shipping destination of the solution, and a shipping interval of the solution; work notification means for notifying the start of work to ship the solution; and history registration means for registering the shipping date of the solution in the customer data as shipping history, and the work notification means includes first work start notification means for notifying the start of work to ship the solution and an injector for injecting the solution to the shipping destination when the customer data does not include the shipping history. and a second work start notification means for notifying the start of work to ship the solution to the destination but not ship the sprayer to the destination at a timing based on the shipping date in the latest shipping history of the customer data and the scheduled shipping date calculated based on the shipping interval of the customer data when the customer data includes a shipping history, and further comprising a first deadline notification means for notifying the contact person of the expiration date of the solution before the expiration date of the solution, and a second deadline notification means for notifying the contact person of the re-application deadline before the re-application deadline, which is the deadline for re-application after application, which is the act of spraying the solution onto an item using a sprayer.

[0010] Preferably, the above-mentioned shipping server includes a data input receiving means for receiving input of contact information, shipping destination, and shipping interval, and a storage means for storing the contact information, shipping destination, and shipping interval received by the data input receiving means as new customer data.

[0011] Preferably, the above shipping server further comprises an expiration date calculation means for calculating the expiration date of the solution based on the shipping date in the shipping history of the customer data, and the first expiration date notification means notifies the contact person of the expiration date of the solution calculated by the expiration date calculation means before the expiration date of the solution calculated by the expiration date calculation means.

[0012] Preferably, the above shipping server further comprises a history receiving means for receiving input of the expiration date of the solution, the history registration means registers the expiration date of the solution received as input by the history receiving means in the customer data as shipping history together with the shipping date, and the first expiration date notification means notifies the contact person of the expiration date of the solution registered in the shipping history of the customer data before the expiration date of the solution registered in the shipping history of the customer data.

[0013] Preferably, the above-mentioned shipping server further includes a first re-construction deadline calculation means for calculating a re-construction deadline based on the shipping date in the shipping history of the customer data, and a second deadline notification means for notifying the contact point of the re-construction deadline calculated by the first re-construction deadline calculation means prior to the re-construction deadline calculated by the first re-construction deadline calculation means.

[0014] Preferably, the above-mentioned shipping server further comprises a construction date input acceptance means for accepting input of the construction date, which is the date on which construction was carried out, and a second re-construction deadline calculation means for calculating the re-construction deadline based on the construction date accepted by the construction date input acceptance means, and the second deadline notification means notifies the contact point of the re-construction deadline calculated by the second re-construction deadline calculation means prior to the re-construction deadline calculated by the second re-construction deadline calculation means.

[0015] In the above-mentioned shipping server, preferably, the first deadline notification means notifies the contact person of the expiration date of the solution a first number of days before the expiration date of the solution, and the second deadline notification means notifies the contact person of the re-application deadline a second number of days before the re-application deadline.

[0016] In the shipping server, preferably, the first and second deadline notification means notify the contact person at the same timing on a date that is the third number of days after the shipping date of the solution.

[0017] A control method for a shipping server according to another aspect of the present invention is a shipping server that manages shipping of a solution containing a photocatalyst to a customer, the shipping server having storage means for storing customer data, which is data relating to the customer, including at least the customer's contact information, a shipping destination of the solution, and a shipping interval of the solution, and the method includes a work notification step of notifying the start of work to ship the solution, a history reception step of receiving input of a shipping date of the solution, and a history registration step of registering the shipping date received in the history reception step as shipping history in the customer data, and the work notification step includes a step of notifying the start of work to ship the solution when the customer data does not include shipping history, and a step of registering the solution and a spraying step of spraying the solution when the customer data does not include shipping history. The method includes a first work start notification step of notifying the start of work to ship the solution to the shipping destination without shipping the sprayer to the shipping destination, and a second work start notification step of notifying the start of work to ship the solution to the shipping destination but not ship the sprayer to the shipping destination at a timing based on a scheduled shipping date calculated based on the shipping date in the latest shipping history of the customer data and the shipping interval of the customer data, if the customer data includes a shipping history, and further includes a first deadline notification step of notifying the contact person of the expiration date of the solution before the expiration date of the solution, and a second deadline notification step of notifying the contact person of the re-application deadline before the re-application deadline, which is the deadline for re-application after application, which is the act of spraying the solution onto an item using a sprayer. [Effects of the Invention]

[0018] According to the present invention, it is possible to provide a shipping server and a shipping server control method that can improve convenience for builders who are customers. [Brief explanation of the drawings]

[0019] [Figure 1] FIG. 1 is a diagram showing an overview of a photocatalyst delivery service in one embodiment of the present invention. [Figure 2] FIG. 10 is a diagram illustrating the reapplication deadline and the expiration date of the bottle. [Figure 3] 1 is a diagram showing the configuration of a photocatalyst delivery system in one embodiment of the present invention. [Figure 4]10 is a flowchart showing an application acceptance process performed by a shipping server 100 according to an embodiment of the present invention. [Figure 5] FIG. 2 is a diagram schematically showing an application screen displayed on the display device of customer terminal 200 in one embodiment of the present invention. [Figure 6] FIG. 6 is a diagram schematically showing the contents of customer database 110 immediately after the contents entered on the application screen shown in FIG. 5 are registered as new customer data in one embodiment of the present invention. [Figure 7] 10 is a flowchart showing a shipping process performed by the shipping server 100 in one embodiment of the present invention. [Figure 8] FIG. 10 is a diagram schematically showing customer data immediately after the first delivery is completed (immediately after the process of step S319 in FIG. 7) in one embodiment of the present invention. [Figure 9] FIG. 10 is a diagram schematically showing customer data immediately after the second delivery is completed (immediately after the process of step S319 in FIG. 7) in one embodiment of the present invention. [Figure 10] FIG. 2 is a diagram schematically showing the expiration date and reapplication deadline of a bottle in one embodiment of the present invention. [Figure 11] 10 is a flowchart showing a notification process performed by the shipping server 100 in the embodiment of the present invention. [Figure 12] FIG. 10 is a diagram showing an example of a method for notifying the expiration date of a bottle in an embodiment of the present invention. [Figure 13] FIG. 10 is a diagram illustrating an example of a method for notifying a re-application deadline in an embodiment of the present invention. [Figure 14] FIG. 10 is a diagram schematically showing customer data immediately after the second delivery is completed (immediately after the process of step S319 in FIG. 7) in the first modified example of the embodiment of the present invention. [Figure 15] 10 is a flowchart showing a notification process performed by the shipping server 100 in a first modified example of the embodiment of the present invention. [Figure 16] 10 is a flowchart showing a notification process performed by the shipping server 100 in a second modified example of the embodiment of the present invention. [Figure 17] FIG. 10 is a diagram showing an example of a method for notifying the reapplication deadline and the expiration date of the bottle in a second modified example of an embodiment of the present invention. [Figure 18] 10 is a flowchart showing a change process performed by the shipping server 100 in a third modified example of the embodiment of the present invention. [Figure 19] FIG. 10 is a diagram schematically showing a change screen displayed on the display device of the customer terminal 200 in a third modified example of the embodiment of the present invention. [Figure 20] FIG. 19 is a diagram schematically showing customer data immediately after the construction date is input (immediately after the process of step S719 in FIG. 18) in the third modified example of the embodiment of the present invention. [Figure 21] 10 is a flowchart showing a notification process performed by the shipping server 100 in a third modified example of the embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0020] Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

[0021] [Photocatalyst delivery service overview]

[0022] In this embodiment, the photocatalyst delivery system provides a subscription-based photocatalyst delivery service in which, when an application for use of the photocatalyst delivery service is received from a customer (a contractor), the business operator repeatedly ships bottles (hereinafter referred to as "bottles") filled with a photocatalyst solution, which is a solution containing a photocatalyst, to the customer at the required timing.

[0023] FIG. 1 is a diagram showing an outline of a photocatalyst delivery service according to one embodiment of the present invention.

[0024] Referring to FIG. 1(a), specifically, in the first shipment after accepting an application for the photocatalyst delivery service from a customer CM, the business operator BC will ship a set of a bottle BL and a sprayer GN to the customer CM. The bottle BL is detachable from the sprayer GN. The sprayer GN has the function of spraying the photocatalyst solution filled in the attached bottle BL. The number of sets of bottle BL and sprayer GN shipped will correspond to the number contracted by the customer CM.

[0025] The photocatalytic solution filled in the bottle BL may contain at least a photocatalyst. If the number of contracted units of the customer CM increases or if the injector GN breaks down, the business operator BC may also ship a set of the bottle BL and the injector GN to the customer CM.

[0026] Referring to FIG. 1(b), a customer CM who receives a bottle BL and a sprayer GN attaches the bottle BL to the sprayer GN and sprays the photocatalytic solution filled in the bottle BL toward an item, thereby performing photocatalytic application. The application location is arbitrary, and may be, for example, a facility such as a hospital or a sports gym, the home, or outdoors. Basically, after one photocatalytic application, all of the photocatalytic solution filled in the bottle BL is consumed, and the bottle BL becomes an empty bottle BL1.

[0027] Referring to FIG. 1(c), the business operator BC makes the next shipment on the next scheduled shipment date, which is the date on which the number of days corresponding to the shipping interval desired by the customer CM has passed since the previous shipment date. For the second and subsequent shipments, the business operator BC will only ship the bottles BL to the customer CM, and will not ship the injectors GN. This is because the bottles BL are consumables, while the injectors GN are not. The same number of bottles BL as the number of injectors GN shipped in the first shipment will be shipped.

[0028] Referring to Figure 1(d), the customer CM who has received the bottle BL removes the empty bottle BL1 from the sprayer GN, attaches the new bottle BL that he or she has received, and applies the photocatalyst by spraying the photocatalyst solution filled in the bottle BL toward the item.

[0029] After that, the business operator BC repeats the shipping process shown in Figure 1(c), and the customer CM repeats the installation process shown in Figure 1(d). This allows the customer CM to repeatedly install the photocatalyst at the necessary timing.

[0030] Figure 2 is a diagram explaining the reapplication deadline and the expiration date of the bottle. Figure 2(a) is a diagram explaining the reapplication deadline. Figure 2(b) is a diagram explaining the expiration date of the photocatalytic solution.

[0031] Referring to FIG. 2(a), the sterilization performance of a photocatalytic solution decreases over time from the date of manufacture due to the proliferation of airborne bacteria and the like that have become mixed into the photocatalytic solution, or due to deterioration caused by light or temperature. Therefore, the date on which the sterilization performance of the photocatalytic solution reaches a certain threshold (here, 85% of the sterilization performance of the photocatalytic solution immediately after manufacture) is the expiration date X1 of the bottle (in other words, the expiration date of the solution containing the photocatalyst). The expiration date X1 of the bottle is the period during which the sterilization performance of the photocatalytic solution is maintained. The expiration date X1 of the bottle may be set by the bottle manufacturer or by a business that purchases the bottle from the manufacturer.

[0032] Referring to FIG. 2(b), the adhesive strength of the applied photocatalyst to the surface of an article is weak, so the photocatalyst peels off from the surface of the article due to factors such as contact with human hands or the passage of time, weakening the application effect of the photocatalyst. Therefore, the reapplication deadline X2 is the date on which the application effect of the photocatalyst reaches a certain threshold (here, 65% of the application effect immediately after application). The reapplication deadline X2 is the deadline for reapplication after the previous application. The reapplication deadline X2 is also the deadline for the period during which it is recommended to reapplication before the effect of the previous application is lost.

[0033] [Configuration of the photocatalyst delivery system]

[0034] FIG. 3 is a diagram showing the configuration of a photocatalyst delivery system in one embodiment of the present invention.

[0035] Referring to Fig. 3, the photocatalyst delivery system in this embodiment includes a shipping server 100, a plurality of customer terminals 200, and a plurality of shipping terminals 300. The shipping server 100 is connected to each of the plurality of customer terminals 200 via the Internet 400, and is capable of communicating with each of the customer terminals 200 via the Internet 400. The shipping server 100 is connected to each of the plurality of shipping terminals 300 via an intranet 500, and is capable of communicating with each of the shipping terminals 300 via the intranet 500. The shipping server 100 may be connected to each of the plurality of shipping terminals 300 via the Internet 400.

[0036] The shipping server 100 manages the shipping of the photocatalyst-containing solution to the customer. The shipping server 100 requests the customer's contact to start application before the expiration date of the bottle so that the customer can obtain sufficient disinfecting performance of the photocatalyst solution. The shipping server 100 encourages the customer to reapply the photocatalyst by notifying the customer of the reapplication deadline to maintain the effectiveness of the photocatalyst application by the customer.

[0037] The shipping server 100 includes a CPU (Central Processing Unit) 101 (an example of a work notification means, a history reception means, a history registration means, a first deadline notification means, a second deadline notification means, a data input reception means, an expiration date calculation means, a first re-construction deadline calculation means, a construction date input reception means, and a second re-construction deadline calculation means), a ROM (Read Only Memory) 102, a RAM (Random Access Memory) 103, a storage device 104 (an example of a storage means), a network interface 105, an operation unit 106, and a display unit 107.

[0038] The CPU 101 controls the operation of each part of the delivery server 100 in accordance with a program stored in the ROM 102 or the storage device 104 .

[0039] The ROM 102 stores various programs.

[0040] The RAM 103 is used as a working memory for the CPU 101 .

[0041] The storage device 104 stores various data. In particular, the storage device 104 stores a customer database 110, which will be described later. The customer database 110 contains one or more pieces of customer data, which are data related to customers. The customer data includes a customer number, which is an identifier for identifying the customer, the details of the contract with the customer, a shipping history to the customer, and a next scheduled shipping date, which is the next scheduled shipping date to the customer. The storage device 104 also stores information (such as an IP address) necessary for communication with the shipping terminal 300.

[0042] The network interface 105 communicates with other devices on the Internet 400 and the intranet 500 using a communication protocol such as TCP / IP.

[0043] The operation unit 106 accepts various operations.

[0044] The display unit 107 displays various types of information.

[0045] Each of the multiple customer terminals 200 is a communication terminal used by each of multiple different customers. Each of the multiple shipping terminals 300 is installed at a location where bottles are shipped to customers (such as a branch office or agency of the business) and is used by a worker (employed by the business) who performs the shipping work. Each of the multiple customer terminals 200 and the multiple shipping terminals 300 includes one or more CPUs, memory that constitutes the working area of ​​the CPU, a large-capacity storage device such as a hard disk drive or SSD (Solid State Drive), an input device that accepts input (such as a keyboard, mouse, or touch panel), a display device such as a liquid crystal display device, and a communication unit that connects to an external communication environment such as the Internet.

[0046] [Application acceptance process]

[0047] Next, an application acceptance process will be described, which is a process performed by the shipping server 100 when an application for use of the photocatalyst delivery service is accepted from a new customer.

[0048] 4 is a flowchart showing the application acceptance process performed by shipping server 100 in one embodiment of the present invention. Each of the flowcharts described below is realized by CPU 101 operating in accordance with a program stored in ROM 102 or storage device 104.

[0049] 4, when a new customer applies for use of the photocatalyst delivery service, the customer accesses the shipping server 100 using the customer terminal 200 and performs a predetermined application operation. The CPU 101 determines whether or not the predetermined application operation has been accepted from the customer terminal 200 (S101).

[0050] In step S101, if it is determined that a predetermined application operation has been accepted from the customer terminal 200 (YES in S101), the CPU 101 displays an application screen on the display device of the customer terminal 200 and accepts entries for each item on the application screen (S103). Next, the CPU 101 determines whether pressing of the OK key on the application screen has been accepted (S105).

[0051] In step S105, when it is determined that pressing of the OK key on the application screen has not been accepted (NO in S105), CPU 101 determines whether pressing of the cancel key on the application screen has been accepted (S111).

[0052] In step S105, if it is determined that pressing of the OK key on the application screen has been accepted (YES in S105), CPU 101 determines whether or not entry of necessary items on the application screen has been accepted (S107).

[0053] In step S107, if it is determined that the necessary items on the application screen have been entered (YES in S107), the CPU 101 assigns a customer number to the entered information, registers the entered information as new customer data in the customer database 110 (S109), and terminates the process.

[0054] If it is determined in step S107 that the required fields on the application screen have not been filled in (NO in S107), the CPU 101 notifies the customer that there is an incomplete entry by, for example, displaying a warning on the application screen or sounding a warning on the customer terminal 200 (S113), and proceeds to processing in step S105.

[0055] In step S111, if it is determined that pressing of the cancel key on the application screen has not been accepted (NO in S111), CPU 101 proceeds to the process of step S105.

[0056] If it is determined in step S101 that the specified application operation has not been accepted from the customer terminal 200 (NO in S101), or if it is determined in step S111 that the press of the cancel key on the application screen has been accepted (YES in S111), the CPU 101 terminates the processing.

[0057] The shipping server 100 may accept an application operation by a customer or a business operator through the operation unit 106 without going through the customer terminal 200. In this case, the application screen is displayed on the display unit 107.

[0058] FIG. 5 is a diagram schematically showing an application screen displayed on the display device of the customer terminal 200 in one embodiment of the present invention.

[0059] Referring to FIG. 5, the application screen includes boxes BX1 to BX6, combo boxes CB1 and CB2, an OK key KY1, and a cancel key KY2.

[0060] Box BX1 accepts the customer's contact email address. Box BX2 accepts the customer's desired password. Box BX3 accepts the customer's name. Box BX4 accepts the customer's affiliation. Box BX5 accepts the customer's shipping address (in this case, address) to which the bottle should be sent. Box BX6 accepts the customer's contact phone number.

[0061] Combo box CB1 accepts the customer's desired number of sprayers, for example, between 1 and 99. Combo box CB2 accepts the customer's desired interval for bottle delivery, for example, 1 week, 2 weeks, 3 weeks, 1 month, or 2 months.

[0062] The OK key KY1 is pressed to confirm the details entered on the application screen, and the cancel key KY2 is pressed to discard the details entered on the application screen and close the application screen.

[0063] FIG. 6 is a diagram showing in schematic form the contents of customer database 110 immediately after the details entered on the application screen shown in FIG. 5 have been registered as new customer data in one embodiment of the present invention.

[0064] 5 and 6, a new customer number (here, the customer number is "4") is assigned to the new customer data. The details of each item entered on the application screen shown in FIG. 5 are registered in each item of the contract details of the new customer data.

[0065] Specifically, the contract details of the customer data include the following items: ID (contact information), PASS, name, affiliation, shipping address, telephone number, contract date, contracted number of units, and shipping interval. The email address entered on the application screen is registered in the ID (contact information) field of the contract details. The desired password entered on the application screen is registered in the PASS field of the contract details. The name entered on the application screen is registered in the name field of the contract details. The affiliation entered on the application screen is registered in the affiliation field of the contract details. The address entered on the application screen is registered in the shipping address field of the contract details. The telephone number entered on the application screen is registered in the telephone field of the contract details. The date the customer data was registered is registered in the contract date field of the contract details. The desired number of units entered on the application screen is registered in the contracted number field of the contract details. The shipping interval entered on the application screen is registered in the shipping interval field of the contract details.

[0066] Immediately after registering new customer data, no bottles have been shipped to the customer. In this case, the next scheduled shipping date and shipping history fields are left blank. The shipping server 100 may enter an appropriate date for the next scheduled shipping date.

[0067] [Shipping Processing]

[0068] Next, a shipping process that is a process performed by the shipping server 100 when a business operator performs shipping work will be described.

[0069] FIG. 7 is a flowchart showing the shipping process performed by shipping server 100 in one embodiment of the present invention.

[0070] Referring to FIG. 7, CPU 101 extracts unextracted customer data from the customer data registered in customer database 110 (S301), and determines whether the extracted customer data includes a shipping history (S303).

[0071] In step S303, if it is determined that the extracted customer data does not contain a shipping history (NO in S303), the extracted customer data belongs to a new customer, and the customer does not own a sprayer. It is necessary to promptly ship a sprayer and the first batch of bottles to the customer of the extracted customer data. In this case, CPU 101 notifies an employee of the start of work to ship the number of sprayers and bottle sets listed in the contract number field of the extracted customer data to the shipping destination of the customer data (in other words, the start of work to ship the first batch to the customer) (S305).

[0072] In step S303, if it is determined that the extracted customer data contains a shipping history (YES in S303), one or more shipments have already been made to the customer of the extracted customer data, and the customer is in possession of the sprayer. In this case, CPU 101 determines whether the next scheduled shipping date for the extracted customer data has arrived (S309). Note that in step S309, it is sufficient to determine whether the timing based on the next scheduled shipping date for the extracted customer data has arrived.

[0073] In step S309, if it is determined that the next scheduled shipping date for the extracted customer data has not arrived (NO in S309), there is no need to ship to the customer of the extracted customer data at this time, so CPU 101 proceeds to processing in step S323.

[0074] In step S309, if it is determined that the next scheduled shipping date for the extracted customer data has arrived (YES in S309), it is necessary to ship the next batch of bottles to the customer of the extracted customer data. In this case, CPU 101 notifies an employee of the start of a process to ship the number of bottles listed in the contract number field of the extracted customer data to the shipping address of the customer data, but not to ship the sprayers to the shipping address of the customer data (S311). Note that since the customer still has the sprayers that were shipped in the first shipment, the sprayers will not be shipped in this process.

[0075] The notifications in steps S305 and S311 are performed, for example, by displaying a predetermined message on the display unit 107 of the shipping server 100. The notifications in steps S305 and S311 may also be performed by sending a notification to the shipping terminal 300 used by the employee in charge of shipping.

[0076] The employee who received the notification in step S305 ships the sprayer and bottle to the customer associated with the extracted customer data. The employee who received the notification in step S311 ships the bottle to the customer associated with the extracted customer data. When performing these shipping operations, the employee inputs information about the bottle to be shipped into shipping server 100. The employee may access customer database 110 stored in shipping server 100 through shipping terminal 300 and input information about the bottle to be shipped in the shipping history field of the extracted customer data. The employee may also input information about the bottle to be shipped by sending an email from shipping terminal 300 to shipping server 100, for example.

[0077] The bottle information to be input here is the bottle's serial number. The employee who has received the notification in step S305 may input the sprayer information along with the bottle information.

[0078] Following the processing of step S305 or S311, when CPU 101 receives input of bottle information from an employee (S313), it creates a new shipping history in the shipping history field of the extracted customer data (S315) and registers the input information and shipping date in the new shipping history (S317). The shipping date may be the one entered by the employee. Next, CPU 101 calculates the next scheduled shipping date based on the shipping date in the most recent shipping history of the extracted customer data and the shipping interval registered in the extracted customer data (S319). The next scheduled shipping date is the shipping date in the most recent shipping history plus the interval (number of days) entered in the shipping interval field. Next, CPU 101 registers the calculated date as the next scheduled shipping date for the extracted customer data (S321) and proceeds to the processing of step S323.

[0079] In step S323, CPU 101 determines whether or not all customer data registered in customer database 110 has been extracted (S323).

[0080] In step S323, if it is determined that all customer data registered in customer database 110 will not be extracted (NO in S323), CPU 101 proceeds to the process of step S301.

[0081] If it is determined in step S323 that all customer data registered in customer database 110 has been extracted (YES in S321), CPU 101 ends the process.

[0082] FIG. 8 is a diagram schematically showing customer data immediately after the first delivery is completed (immediately after the processing of step S319 in FIG. 7) in one embodiment of the present invention.

[0083] Referring to Figure 8, the column for the first shipment ("Shipment 1") in the shipping history of the customer data contains the shipping date and the serial numbers of the bottles that were shipped. Since the contracted number of units for the customer data is two, the serial numbers of the bottles for both units are registered. In addition, the next scheduled shipping date for the customer data is registered as the shipping date (May 1, 2020) plus the shipping interval (one month) (June 1, 2020).

[0084] FIG. 9 is a diagram schematically showing customer data immediately after the second delivery is completed (immediately after the processing of step S319 in FIG. 7) in one embodiment of the present invention.

[0085] Referring to Figure 9, the column for the second shipment ("Shipment 2") in the shipping history of the customer data contains the shipping date and the serial numbers of the bottles that were shipped. Since the contracted number of units for the customer data is two, the serial numbers of the bottles for both units are registered. In addition, the next scheduled shipping date for the customer data is registered as the latest shipping date (June 1, 2020) plus the shipping interval (one month) (July 1, 2020).

[0086] [Notification Processing]

[0087] Next, a notification process will be described, which is a process in which the shipping server 100 notifies the customer of the expiration date and the reconstruction deadline of the bottle.

[0088] FIG. 10 is a diagram schematically showing the expiration date and the reconstruction deadline of the bottle in one embodiment of the present invention. In FIG. 10, the respective shipping dates of the first and second bottles are shown as "shipping date 1" and "shipping date 2", respectively. The manufacturing date of the bottle shipped the second time is denoted as "manufacturing date 2". The expiration date of the bottle shipped on the second shipping date is denoted as "bottle expiration date 2". The date of construction (first construction date) using the bottle shipped the first time is denoted as "construction date 1". The deadline for performing the second construction using the bottle shipped on the second shipping date after performing the construction using the bottle shipped on the first shipping date (the deadline for the second construction) is denoted as "construction deadline 2".

[0089] Referring to FIG. 10(a), attention is paid to the bottle shipped the second time. The manufacturing date ("manufacturing date 2") of the bottle shipped the second time is presumed to be a date approximately a certain number of days before the shipping date ("shipping date 2") of the second bottle. For this reason, the expiration date ("bottle expiration date 2") of the bottle shipped the second time is presumed to be a date after a predetermined number of days PA (<X1 (FIG. 2)) have elapsed from the shipping date ("shipping date 2") of the second bottle.

[0090] Therefore, the shipping server 100 calculates the expiration date ("bottle expiration date 2") of the bottle shipped the second time based on the shipping date ("shipping date 2") of the second bottle. Before the calculated expiration date ("bottle expiration date 2") of the bottle shipped the second time, the shipping server 100 notifies the contact information of the customer data of the calculated expiration date ("bottle expiration date 2") of the bottle shipped the second time. This notification is preferably performed at a timing TA that is a first number of days (for example, 2 to 3 days) before the expiration date ("bottle expiration date 2") of the bottle shipped the second time.

[0091] Referring to Figure 10(b), let's focus on the first bottle shipped. Customers are encouraged to install the bottle as soon as possible after it arrives. Therefore, it is estimated that the date of the first installation performed by the customer ("Installation Date 1") is approximately a certain number of days after the shipping date of the first bottle ("Shipping Date 1"). Therefore, it is estimated that the deadline for the second installation ("Installation Deadline 2") is a certain number of days PB (>X2 (Figure 2)) after the shipping date of the first bottle ("Shipping Date 1").

[0092] Therefore, the shipping server 100 calculates the deadline for the second application ("Execution Deadline 2") based on the shipping date of the first bottle ("Shipping Date 1"). The shipping server 100 notifies the contact point in the customer data of the calculated deadline for the second application ("Execution Deadline 2") prior to the calculated deadline for the second application ("Execution Deadline 2"). This notification is preferably made at timing TB, a second number of days (for example, 2 to 3 days) before the deadline for the second application ("Execution Deadline 2").

[0093] FIG. 11 is a flowchart showing the notification process performed by the shipping server 100 in one embodiment of the present invention.

[0094] Referring to FIG. 11, CPU 101 extracts unextracted customer data from the customer data registered in customer database 110 (S501), and determines whether the extracted customer data includes a shipping history (S503).

[0095] In step S503, if it is determined that the extracted customer data does not include a shipping history (NO in S503), there is no need to notify the customer of the extracted customer data. In this case, CPU 101 proceeds to the process of step S517.

[0096] In step S503, if it is determined that the extracted customer data includes a shipping history (YES in S503), CPU 101 calculates the re-application deadline based on the shipping date in the shipping history of the extracted customer data (S505). Next, CPU 101 determines whether the timing is a second number of days before the calculated re-application deadline (S507).

[0097] If it is determined in step S507 that the timing is the second number of days before the calculated re-application deadline (YES in S507), CPU 101 encourages the customer to re-application by notifying the contact information in the customer data of the calculated re-application deadline (S509), and proceeds to processing of step S511.

[0098] In step S507, if it is determined that the timing is not the second number of days before the calculated re-application deadline (NO in S507), it is not the timing to notify the re-application deadline, so CPU 101 proceeds to processing in step S511.

[0099] In step S511, CPU 101 calculates the expiration date of the bottle based on the shipping date in the shipping history of the extracted customer data (S511). Next, CPU 101 determines whether the timing is a first number of days before the calculated expiration date of the bottle (S513).

[0100] In step S513, if it is determined that the timing is the first number of days before the calculated expiration date of the bottle (YES in S513), CPU 101 requests the customer to perform the application by notifying the contact information in the customer data of the calculated expiration date of the bottle (S515), and proceeds to processing in step S517.

[0101] In step S513, if it is determined that the timing is not the first number of days before the calculated expiration date of the bottle (NO in S513), it is not the timing to notify the expiration date of the bottle, so CPU 101 proceeds to the process of step S517.

[0102] In step S517, CPU 101 determines whether or not all customer data registered in customer database 110 has been extracted (S517).

[0103] In step S517, if it is determined that all customer data registered in customer database 110 will not be extracted (NO in S517), CPU 101 proceeds to the process of step S501.

[0104] In step S517, if it is determined that all customer data registered in customer database 110 has been extracted (YES in S517), CPU 101 ends the process.

[0105] FIG. 12 is a diagram showing an example of a method for notifying the expiration date of a bottle in one embodiment of the present invention.

[0106] 12, methods for notifying the contact person in the customer data of the expiration date of the bottle include, for example, sending an email to the customer's email address registered in the customer data, or notifying by telephone. When notifying by email, the email message may include the expiration date of the shipped bottle and a request to complete the installation by the expiration date of the bottle.

[0107] FIG. 13 is a diagram showing an example of a method for notifying a re-application deadline in an embodiment of the present invention.

[0108] 13, methods for notifying the contact point in the customer data of the reapplication deadline include, for example, sending an email to the customer's email address registered in the customer data, or notifying by telephone. When notifying by email, the email message may include the deadline for application using the shipped bottles (reapplication deadline) and an encouragement to complete the application by the reapplication deadline.

[0109] [First Modification]

[0110] As a first variant, in the shipping processing flowchart shown in Figure 7, when the shipping server 100 accepts input of bottle information from an employee (step S313), it may also accept input of the bottle's expiration date, and when registering the input information and shipping date in the shipping history (S317), it may register the input bottle's expiration date in the shipping history field of the customer data.

[0111] Fig. 14 is a diagram schematically showing customer data immediately after the second shipment is completed (immediately after the processing of step S319 in Fig. 7) in the first modified example of an embodiment of the present invention. Fig. 14 is a diagram corresponding to Fig. 9.

[0112] Referring to Figure 14, in the column for the second shipment ("Shipment 2") in the shipping history of the customer data, the manufacturing date of the shipped bottles is registered in addition to the shipping date and the manufacturing number of the shipped bottles. Since the number of contracted bottles in the customer data is two, the manufacturing dates of the bottles for two bottles are registered. Note that when multiple different manufacturing dates of bottles are registered, it is preferable that notification of the bottle expiration dates be sent before the expiration date of the bottle that is the earliest from the current time among the expiration dates of the multiple bottles.

[0113] FIG. 15 is a flowchart showing the notification process performed by the shipping server 100 in the first modified example of the embodiment of the present invention.

[0114] 15, this flowchart differs from the flowchart shown in FIG. 11 in that the processing in step S531 is performed instead of the processing in step S511.

[0115] In step S531, CPU 101 refers to the expiration date of the bottle registered in the shipping history of the extracted customer data (S531). Next, CPU 101 determines whether the timing is a first number of days before the expiration date of the referenced bottle (S513).

[0116] In step S513, if it is determined that the timing is the first number of days before the expiration date of the referenced bottle (YES in S513), CPU 101 encourages the customer to reapply the product by notifying the contact information in the customer data of the expiration date of the referenced bottle (S515), and proceeds to processing in step S517.

[0117] In step S513, if it is determined that the timing is not the first number of days before the expiration date of the referenced bottle (NO in S513), it is not the timing to notify the expiration date of the bottle, so CPU 101 proceeds to processing in step S517.

[0118] According to the first variant, the expiration date of the inputted bottle is notified, so that a more appropriate expiration date can be notified to the customer compared to notifying the expiration date of the bottle calculated based on the shipping date.

[0119] [Second Modification]

[0120] As a second variation, the shipping server 100 may notify the customer's contact information of the bottle's expiration date and reapplication deadline at the same time on a date that is a third number of days (for example, 2 to 3 days) after the bottle's shipping date.

[0121] FIG. 16 is a flowchart showing the notification process performed by the shipping server 100 in the second modified example of the embodiment of the present invention.

[0122] Referring to FIG. 16, CPU 101 extracts unextracted customer data from the customer data registered in customer database 110 (S541), and determines whether the extracted customer data includes a description of shipping history (S543).

[0123] In step S543, if it is determined that the extracted customer data contains a shipping history (YES in S543), CPU 101 determines whether the third number of days has passed since the shipping date in the latest shipping history of the customer data (S545).

[0124] If it is determined in step S545 that the third number of days has passed since the shipping date in the shipping history of the customer data (YES in S545), CPU 101 calculates the reapplication deadline based on the shipping date in the extracted shipping history of the customer data (S547), and calculates the expiration date of the bottle based on the shipping date in the extracted shipping history of the customer data (S549). Next, CPU 101 notifies the contact point in the customer data of the calculated reapplication deadline and the expiration date of the bottle (S551), and proceeds to the processing of step S553.

[0125] If it is determined in step S543 that the extracted customer data does not contain a shipping history (NO in S543), or if it is determined in step S545 that the date is not the third day after the shipping date in the customer data's shipping history (NO in S545), it is not time to send a notification, so CPU 101 proceeds to processing of step S553.

[0126] In step S553, CPU 101 determines whether or not all customer data registered in customer database 110 has been extracted (S553).

[0127] In step S553, if it is determined that all customer data registered in customer database 110 will not be extracted (NO in S553), CPU 101 proceeds to the process of step S541.

[0128] In step S553, if it is determined that all customer data registered in customer database 110 has been extracted (YES in S553), CPU 101 ends the process.

[0129] FIG. 17 is a diagram showing an example of a method for notifying the reapplication deadline and the expiration date of the bottle in the second modified example of the embodiment of the present invention.

[0130] 17, methods for notifying the contact point in customer data of the reapplication deadline and the expiration date of the bottles include, for example, sending an email to the customer's email address registered in the customer data, or notifying by telephone. When notifying by email, the email message may include the deadline for application using the shipped bottles (reapplication deadline), an encouragement to complete application by the reapplication deadline, the expiration date of the shipped bottles, and a request to complete application by the expiration date of the bottles.

[0131] According to the second modification, the expiration date of the bottle and the reapplication deadline are notified to the customer's contact point at the same time, so that the processing of the shipping server 100 can be simplified.

[0132] [Third Modification]

[0133] As a third modification, the shipping server 100 may receive input of the installation date from the customer, and calculate the re-installation deadline based on the input installation date.

[0134] 18 is a flowchart showing the change processing performed by the shipping server 100 in the third modified example of an embodiment of the present invention. The change processing is a process performed by the shipping server 100 when an input to change customer data (including an input to register a construction date in the customer data) is received.

[0135] 18, when a new customer changes customer data, the new customer accesses shipping server 100 using customer terminal 200 and performs a predetermined change operation. CPU 101 determines whether or not the predetermined change operation has been accepted (S701).

[0136] In step S701, if it is determined that a predetermined change operation has been received from the customer terminal 200 (YES in S701), the CPU 101 displays a change screen on the display device of the customer terminal 200 and receives changes to each item on the change screen (S703). Next, the CPU 101 determines whether or not pressing of the OK key on the change screen has been received (S705).

[0137] In step S705, if it is determined that pressing of the OK key in the change screen has not been accepted (NO in S705), CPU 101 determines whether pressing of the cancel key in the change screen has been accepted (S707).

[0138] In step S705, if it is determined that pressing of the OK key on the change screen has been accepted (YES in S705), CPU 101 reflects the changes accepted on the change screen in the customer data (S709), and proceeds to the processing of step S711.

[0139] In step S707, if it is determined that pressing of the cancel key on the change screen has not been accepted (NO in S707), CPU 101 proceeds to the process of step S705.

[0140] In step S711, CPU 101 determines whether or not there has been a change in the shipping interval registered in the customer data (S711).

[0141] If it is determined in step S711 that the shipping interval has changed (YES in S711), CPU 101 calculates the next shipping date based on the shipping date in the latest shipping history of the customer data and the shipping interval after the change (S713). Next, CPU 101 updates the next shipping date in the customer data to the calculated next shipping date (S715), and proceeds to the processing of step S717.

[0142] In step S711, if it is determined that there is no change in the shipping interval (NO in S711), CPU 101 proceeds to the process of step S717.

[0143] In step S717, CPU 101 determines whether or not input of the construction date has been accepted on the change screen (S717).

[0144] In step S717, if it is determined that input of the installation date has been accepted on the change screen (YES in S717), CPU 101 registers the installation date in the shipping history of the customer data (S719), and ends the process.

[0145] If in step S701 it is determined that the specified application operation has not been accepted from the customer terminal 200 (NO in S701), if in step S707 it is determined that the press of the cancel key on the change screen has been accepted (YES in S707), or if in step S717 it is determined that the input of the construction date has not been accepted on the change screen (NO in S717), the CPU 101 terminates processing.

[0146] The shipping server 100 may accept a change operation by a customer or a business operator through the operation unit 106 without going through the customer terminal 200. In this case, a change screen is displayed on the display unit 107.

[0147] FIG. 19 is a diagram schematically showing a change screen displayed on the display device of the customer terminal 200 in the third modified example of the embodiment of the present invention.

[0148] 19, the change screen includes boxes BX11 to BX16, combo boxes CB11 to CB15, an OK key KY11, and a cancel key KY12. The customer fills in only the items that need to be changed on the change screen, and leaves the items that do not need to be changed blank.

[0149] Box BX11 accepts the customer's changed email address. Box BX12 accepts the customer's changed password. Box BX13 accepts the customer's changed name. Box BX14 accepts the customer's changed affiliation. Box BX15 accepts the customer's changed bottle shipping address (address in this case). Box BX16 accepts the customer's changed phone number.

[0150] Combo box CB11 accepts entry of the number of sprayers (bottles) after the customer's change. Combo box CB12 accepts entry of the bottle delivery interval after the customer's change. Combo boxes CB13 to CB15 accept entry of the installation date.

[0151] The OK key KY11 is pressed to confirm the content entered on the change screen, and the Cancel key KY12 is pressed to discard the content entered on the change screen and close the change screen.

[0152] Fig. 20 is a diagram schematically showing customer data immediately after the construction date is input (immediately after the processing of step S719 in Fig. 18) in the third modified example of an embodiment of the present invention. Fig. 20 is a diagram corresponding to Fig. 9.

[0153] Referring to Figure 20, in the column for the second shipment ("Shipment 2") in the shipping history of the customer data, in addition to the manufacturing number of the shipped bottle, the installation date (the date of installation using the shipped bottle) is registered.

[0154] FIG. 21 is a flowchart showing the notification process performed by the shipping server 100 in the third modified example of the embodiment of the present invention.

[0155] 21, this flowchart differs from the flowchart shown in FIG. 11 in that steps S571 to S577 are performed after the process of step S503.

[0156] In step S503, if it is determined that the extracted customer data contains a shipping history (YES in S503), CPU 101 determines whether the construction date field in the latest shipping history of the extracted customer data is blank (S571).

[0157] In step S571, if it is determined that the field for the installation date in the latest shipping history of the extracted customer data is not blank (NO in S571), installation using the latest bottle has already been performed, meaning that notification is not necessary. In this case, CPU 101 proceeds to the process of step S517.

[0158] In step S571, if it is determined that the application date field in the latest shipping history of the extracted customer data is blank (YES in S571), which means that application using the latest bottle has not yet been performed. In this case, CPU 101 determines whether the second most recent application date in the shipping history of the extracted customer data is listed (S573).

[0159] If it is determined in step S573 that the construction date in the second most recent shipping history of the extracted customer data is listed (YES in S573), CPU 101 calculates the re-construction deadline based on that construction date (S575) and proceeds to processing in step S507.

[0160] If it is determined in step S573 that the second most recent installation date in the shipping history of the extracted customer data is not listed (NO in S573), CPU 101 calculates the re-installation deadline based on the shipping date in the shipping history (S577) and proceeds to processing of step S507.

[0161] According to the third modification, the re-construction deadline is calculated based on the input construction date, so that the customer can be notified of a more accurate re-construction deadline, improving the convenience of the customer (constructor). In addition, the business operator can grasp the progress of the construction by the customer based on whether or not the construction date has been input.

[0162] The configuration of the delivery system in each of the first to third modified examples and the operations other than those described above are similar to those of the delivery system in the above-described embodiment, and therefore description thereof will not be repeated.

[0163] [Effects of the embodiment]

[0164] In the above-described embodiment and modified example, a bottle of photocatalyst is shipped to a customer when needed, the expiration date of the bottle is notified to the customer's contact information before the expiration date, and the reapplication deadline is notified to the customer's contact information before the reapplication deadline. This allows the customer to remember to apply the photocatalyst when needed. As a result, the convenience of the customer, who is the installer, can be improved.

[0165] [others]

[0166] The bottle information may be input by the customer or the like through the customer terminal 200. The construction date may be input by the business or the like through the operation unit 106 of the shipping server 200 or the shipping terminal 300.

[0167] The above-described embodiments and modifications may be combined with each other. For example, the re-application deadline calculated by the method described in the third modification may be notified to the customer at the timing described in the second modification.

[0168] The processes in the above-described embodiments and variations may be performed by software or hardware circuits. A program for executing the processes in the above-described embodiments may be provided, or the program may be recorded on a recording medium such as a CD-ROM, a flexible disk, a hard disk, a ROM, a RAM, or a memory card and provided to a user. The program is executed by a computer such as a CPU. The program may also be downloaded to a device via a communication line such as the Internet.

[0169] The above-described embodiments and modifications should be considered to be illustrative in all respects and not restrictive. The scope of the present invention is defined by the claims, not by the above description, and is intended to include all modifications within the meaning and scope of the claims. [Explanation of symbols]

[0170] 100 Shipping Server (Example of a shipping server) 101 CPU (Central Processing Unit) (an example of a work notification means, a history reception means, a history registration means, a first deadline notification means, a second deadline notification means, a data input reception means, an expiration date calculation means, a first re-work deadline calculation means, a work date input reception means, and a second re-work deadline calculation means) 102 ROM (Read Only Memory) 103 RAM (Random Access Memory) 104 Storage device (an example of storage means) 105 Network Interface 106 Operation section 107 Display section 110 Customer Database 200 customer terminals 300 Shipping Terminal 400 Internet 500 Intranet BL, BL1 bottle BX1~BX6, BX11~BX16 Boxes CB1, CB2, CB11 to CB15 combo boxes KY1, KY2, KY11, KY12 keys Timing of TA and TB notification

Claims

1. A shipping server that manages shipping of a solution containing a photocatalyst to a customer includes: storage means for storing customer data, which is data relating to the customer, including at least the customer's contact information, a shipping destination of the solution, and a shipping interval of the solution; work notification means for notifying the start of work to ship the solution; and history registration means for registering the shipping date of the solution as shipping history in the customer data, wherein the work notification means includes first work start notification means for notifying the start of work to ship the solution and an injector for injecting the solution to the shipping destination when the customer data does not include the shipping history; and In this case, the shipping server includes a second work start notification means that notifies the start of work to ship the solution to the shipping destination and not ship the sprayer to the shipping destination at a timing based on the shipping date in the latest shipping history of the customer data and the scheduled shipping date calculated based on the shipping interval of the customer data, and further includes a first deadline notification means that notifies the contact person of the expiration date of the solution before the expiration date of the solution, and a second deadline notification means that notifies the contact person of the re-application deadline before the re-application deadline, which is the deadline for performing the application again after performing the application, which is the act of spraying the solution onto an item using the sprayer.

2. 2. The shipping server of claim 1, further comprising: a data input receiving means for receiving input of the contact information, the shipping destination, and the shipping interval; and a storage means for storing the contact information, the shipping destination, and the shipping interval received by the data input receiving means as new customer data.

3. The shipping server of claim 1 or 2 further comprises an expiration date calculation means for calculating the expiration date of the solution based on the shipping date in the shipping history of the customer data, and the first expiration date notification means notifies the contact person of the expiration date of the solution calculated by the expiration date calculation means before the expiration date of the solution calculated by the expiration date calculation means.

4. The shipping server of claim 1 or 2 further comprises a history receiving means for receiving input of the expiration date of the solution, wherein the history registration means registers the expiration date of the solution received as input by the history receiving means in the customer data as the shipping history together with the shipping date, and the first expiration date notification means notifies the contact person of the expiration date of the solution registered in the shipping history of the customer data before the expiration date of the solution registered in the shipping history of the customer data.

5. A shipping server as described in any one of claims 1 to 4, further comprising a first re-construction deadline calculation means for calculating the re-construction deadline based on the shipping date of the shipping history of the customer data, and the second deadline notification means notifies the contact point of the re-construction deadline calculated by the first re-construction deadline calculation means before the re-construction deadline calculated by the first re-construction deadline calculation means.

6. A shipping server as described in any one of claims 1 to 4, further comprising a construction date input acceptance means for accepting input of a construction date, which is the date on which the construction was carried out, and a second re-construction deadline calculation means for calculating the re-construction deadline based on the construction date accepted by the construction date input acceptance means, wherein the second deadline notification means notifies the contact person of the re-construction deadline calculated by the second re-construction deadline calculation means before the re-construction deadline calculated by the second re-construction deadline calculation means.

7. A shipping server as described in any one of claims 1 to 6, wherein the first deadline notification means notifies the contact person of the expiration date of the solution a first number of days before the expiration date of the solution, and the second deadline notification means notifies the contact person of the re-application deadline a second number of days before the re-application deadline.

8. The shipping server according to any one of claims 1 to 6, wherein each of the first and second deadline notification means notifies the contact person at the same time on a date that is a third number of days after the shipping date of the solution.

9. A control method for a shipping server that manages shipping of a solution containing a photocatalyst to a customer, the method comprising: storing customer data, which is data relating to the customer, including at least the customer's contact information, a shipping destination of the solution, and a shipping interval of the solution; a work notification step of notifying the start of work to ship the solution; and a history registration step of registering the shipping date of the solution in the customer data as shipping history, the work notification step including a first work start notification step of notifying the start of work to ship the solution and an injector for injecting the solution to the shipping destination when the customer data does not include the shipping history; a second work start notification step for notifying the start of work to ship the solution to the shipping destination but not ship the sprayer to the shipping destination at a timing based on the shipping date in the latest shipping history of the customer data and a scheduled shipping date calculated based on the shipping interval of the customer data when the shipping history includes a shipping history; and a first deadline notification step for notifying the contact point of the expiration date of the solution before the expiration date of the solution; and a second deadline notification step for notifying the contact point of the re-application deadline before the re-application deadline, which is the deadline for performing the application again after performing the application, which is the act of spraying the solution onto an item using the sprayer.

Images