Information processing method, information processing system, and information processing device.

Abstract

To provide an information processing method for properly managing batteries sold as single-use items. [Solution] The information processing method is an information processing method in which a first information processing device 10 and a server 20 connected to the first information processing device 10 via a network work in cooperation, wherein the first information processing device 10 acquires inbound / outbound information that identifies the arrival of lead-acid batteries 47 to a battery shelf 40 installed in a retail store and the outbound / outbound information of lead-acid batteries 47 from the battery shelf 40, and a battery ID (Identifier) ​​that identifies the lead-acid batteries 47 related to the inbound / outbound information, and transmits the battery ID, a retail store ID that identifies the retail store, and the inbound / outbound information in association with each other to the server 20, and the server 20 records the received battery ID, the retail store ID, and the inbound / outbound information in association with each other in a manufacturing database.

Description

Technical Field

[0006] , , , ,

[0001] The present invention relates to an information processing method, an information processing system, and an information processing apparatus.

Background Art

[0002] An information processing method for operating a battery has been proposed in which a battery mounted on an electric vehicle is replaced with a charged battery at a battery exchange station as needed, and the used battery is charged at a bulk charging station (Patent Document 1). The user of the electric vehicle does not own the battery itself and pays a usage fee according to the number of exchanges and the like.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0007] In one respect, it can provide information processing methods for properly managing batteries sold as single-use items. [Brief explanation of the drawing]

[0008] [Figure 1] This is an explanatory diagram illustrating the configuration of the inventory management system. [Figure 2] This is an explanatory diagram illustrating the configuration of the inventory management system. [Figure 3] This is a perspective view of the battery compartment where the batteries are housed. [Figure 4] This is an explanatory diagram illustrating the record layout of the manufacturing database. [Figure 5] This is an explanatory diagram illustrating the record layout of the shelf inventory database. [Figure 6] This is a flowchart illustrating the processing flow of a program in the first information processing device. [Figure 7] This is a flowchart illustrating the processing flow of the subroutine for handling empty positions. [Figure 8] This is a flowchart illustrating the processing flow of a program on a server. [Figure 9] This is a flowchart explaining the program's processing flow when a search request is received. [Figure 10] This is an example screen. [Figure 11]It is an explanatory diagram for explaining a battery shelf and a detector of a modification example. [Figure 12] It is an explanatory diagram for explaining a record layout of the manufacturing DB of Embodiment 2. 7> [Figure 13] It is a flowchart for explaining the processing flow of the program of Embodiment 2. [Figure 14] It is a screen example of Embodiment 3. [Figure 15] It is a flowchart for explaining the processing flow of the program in the first information processing apparatus of Embodiment 3. [Figure 16] It is a flowchart for explaining the processing flow of the program in the server of Embodiment 3. [Figure 17] It is a flowchart for explaining the processing flow of the program of Embodiment 4. [Figure 18] It is an explanatory diagram for explaining the configuration of the inventory management system of Embodiment 5.

Modes for Carrying Out the Invention

[0009] [Embodiment 1] FIG. 1 is an explanatory diagram for explaining the configuration of an inventory management system 50. The inventory management system 50 includes a first information processing apparatus 10 managed by a sales store, a server 20 managed by a battery manufacturer or a sales company such as a subsidiary of the battery manufacturer, and a second information processing apparatus 30 used by a salesperson or the like. The salesperson belongs to a manufacturer or a sales company or the like and is in charge of so-called route sales, regularly visiting the sales stores they are in charge of.

[0010] In the present embodiment, the merchandise handled by the salesperson will be described by taking as an example the case where it is a battery 47 used for a starting battery of a vehicle equipped with an engine, such as a gasoline vehicle and a hybrid vehicle. Lead-acid batteries are often used for the battery 47.

[0011] The retailer has a battery shelf 40 for storing the in-stock batteries 47. The battery shelf 40 includes a battery ID (Identifier) uniquely assigned to the battery 47 and a detector 42 for detecting the receipt and shipment of each battery 47. Here, receipt means that the battery 47 is stored in the battery shelf 40, that is, the warehousing into the battery shelf 40, and shipment means that the battery 47 is taken out from the battery shelf 40, that is, the outwarehousing from the battery shelf 40. The detector 42 is connected to the first information processing device 10.

[0012] The receipt and shipment information for identifying the receipt and shipment of the battery 47 and the battery ID uniquely assigned to the battery 47 are notified from the first information processing device 10 to the server 20 and recorded in the manufacturing DB (Database) 62 (see FIG. 2). The inventory status of the battery 47 in each retailer is notified from the server 20 to the second information processing device 30 used by the salesperson in charge of each retailer. Specifically, the receipt and shipment information is, for example, a flag meaning "receipt" or a flag meaning "shipment".

[0013] When an empty shelf occurs in the battery shelf 40, the salesperson delivers a replacement battery 47. The salesperson may propose to the retailer to stock batteries 47 of different models based on, for example, seasons, sales trends in the retailer in charge, and release information of new products. When making the proposal, the salesperson may refer to data such as sales trends recorded in the manufacturing DB 62.

[0014] By promptly delivering the replacement battery 47, the salesperson can reduce the risk that the retailer loses sales opportunities due to out-of-stock. The retailer can promptly provide a new battery 47 to the end user who visited the store due to problems such as battery depletion without making the user wait until the arrival of the battery 47.

[0015] The batteries 47 stored in the battery shelf 40 may be products purchased and owned by the retailer, or they may be products owned by the manufacturer to which the sales representative belongs, and which have entrusted the sale to the retailer. In consignment sales, the manufacturer, as the consignor, generally has the authority to decide which models of batteries 47 to stock in the battery shelf 40. However, by consulting with the retailer, as the consignee, regarding the models to be stocked, the sales representative can strengthen their relationship with the retailer and achieve high sales performance.

[0016] Figure 2 is an explanatory diagram illustrating the configuration of the inventory management system 50. As mentioned above, the inventory management system 50 includes a first information processing device 10, a server 20, and a second information processing device 30. The battery shelf 40 installed in the store is equipped with a detector 42. An ID tag 48 recording the battery ID and model number is attached to the bottom of the individual packaging box of the battery 47, or to the bottom of the battery 47. The individual packaging box is an example of a container in which the battery 47 is housed.

[0017] The ID tag 48 is, for example, an RFID (Radio Frequency Identification) tag. The detector 42 is, for example, an RFID reader that can read data from the ID tag 48.

[0018] The first information processing device 10 comprises a control unit 11, a main memory 12, an auxiliary memory 13, a communication unit 14, a touch panel 15, and a bus. The touch panel 15 has a display unit 151 and an input unit 152 stacked on the display unit 151.

[0019] The control unit 11 is an arithmetic control device that executes the program of this embodiment. The control unit 11 uses one or more CPUs (Central Processing Units), GPUs (Graphics Processing Units), or multi-core CPUs, etc. The control unit 11 is connected to the hardware components constituting the first information processing device 10 via a bus. The control unit 11 is an example of the first control unit of this embodiment.

[0020] The main memory 12 is a storage device such as SRAM (Static Random Access Memory), DRAM (Dynamic Random Access Memory), or flash memory. The main memory 12 temporarily stores information necessary during processing performed by the control unit 11 and the program currently being executed by the control unit 11.

[0021] The auxiliary storage device 13 is a storage device such as SRAM, flash memory, hard disk, or magnetic tape. The auxiliary storage device 13 stores the shelf inventory DB 61, a program to be executed by the control unit 11, and various data necessary for the execution of the program. The shelf inventory DB 61 may be stored in an external mass storage device connected to the control unit 11. The communication unit 14 is an interface for communication between the first information processing device 10 and the network.

[0022] The touch panel 15 has a configuration in which a display unit 151 is stacked on an input unit 152, such as a liquid crystal display panel or an organic EL (electro-luminescence) panel. The display unit 151 and the input unit 152 may be a separate display device and an input device such as a keyboard, mouse, and microphone.

[0023] The first information processing device 10 is a general-purpose personal computer, tablet, mainframe computer, virtual machine running on a mainframe computer, or quantum computer. The first information processing device 10 may be composed of multiple personal computers or mainframe computers or other hardware that perform distributed processing. The first information processing device 10 may be composed of a cloud computing system. The first information processing device 10 may be composed of multiple personal computers or mainframe computers or other hardware that operate in cooperation. The first information processing device 10 may be dedicated hardware prepared for the information processing method of this embodiment.

[0024] The server 20 comprises a control unit 21, a main memory 22, an auxiliary memory 23, a communication unit 24, and a bus. The control unit 21 is an arithmetic control unit that executes the program of this embodiment. One or more CPUs, GPUs, or multi-core CPUs are used in the control unit 21. The control unit 21 is connected to the hardware components that make up the server 20 via the bus. The control unit 21 is an example of the second control unit of this embodiment.

[0025] The main memory 22 is a storage device such as SRAM, DRAM, or flash memory. The main memory 22 temporarily stores information necessary during processing performed by the control unit 21 and the program currently being executed by the control unit 21.

[0026] The auxiliary storage device 23 is a storage device such as SRAM, flash memory, hard disk, or magnetic tape. The auxiliary storage device 23 stores the manufacturing DB 62, the program to be executed by the control unit 21, and various data necessary for program execution. The manufacturing DB 62 may be stored in an external mass storage device connected to the server 20. The communication unit 24 is an interface for communication between the server 20 and the network.

[0027] Server 20 is a general-purpose personal computer, tablet, mainframe computer, virtual machine running on a mainframe computer, or quantum computer. Server 20 may also be composed of multiple personal computers or mainframe computers performing distributed processing. Server 20 may also be composed of a cloud computing system. Server 20 may also be composed of multiple personal computers or mainframe computers operating in cooperation with each other.

[0028] The second information processing device 30 is an information device used by sales representatives, such as a general-purpose smartphone, tablet, or laptop computer. The configuration of the second information processing device 30 is not shown in the diagrams or description.

[0029] Figure 3 is a perspective view of a battery shelf 40 containing batteries 47. A tablet-type first information processing device 10 is positioned on the top panel of the battery shelf 40 with its touch panel 15 facing forward. The first information processing device 10 may also be attached to the battery shelf 40. If the first information processing device 10 and the touch panel 15 are separate components, the touch panel 15 may be attached to the battery shelf 40 for easy user visibility, while the first information processing device 10 may be placed in a location less visible to the user, such as the underside of the shelf, or in a location away from the battery shelf 40.

[0030] The individual packaging of battery 47 has the model number of battery 47 clearly displayed, making it easy to retrieve the required battery 47 once its model number is known. Note that the battery shelf 40 shown in Figure 3 is an example. The battery shelf 40 may be composed of multiple shelves combined together.

[0031] Multiple detectors 42 are embedded in the shelf on which the battery 47 is placed. The detectors 42 detect the ID tag 48 continuously or periodically, such as every 30 minutes. The detectors 42 transmit whether or not a battery 47 is present and the battery ID of the battery 47 that is present to the first information processing device 10. The shelf may also be provided with partitions so that the detectors 42 and the ID tag 48 are naturally brought into close proximity when a user places a battery 47 on the shelf.

[0032] The battery shelf 40 may have a temperature control function to maintain the temperature of the stored batteries 47 at a temperature of approximately 10°C to 25°C, thereby preventing the deterioration of the batteries 47. The battery shelf 40 may also have a humidity control function to maintain the humidity of the stored batteries 47 at a low level, thereby preventing the deterioration of the batteries 47.

[0033] Figure 4 is an explanatory diagram illustrating the record layout of the manufacturing DB62. The manufacturing DB62 is a database that records the model number of the battery 47, the battery ID, the manufacturing date, the shipping date, the shipping destination ID uniquely assigned to the shipping destination, the arrival date at the shipping destination, and the sales date, linking them together. Note that the battery 47 is shipped not only to retailers but also to automobile manufacturing plants, etc. When the shipping destination is a retailer, the shipping destination ID refers to the retailer ID uniquely assigned to the retailer.

[0034] The manufacturing database 62 has fields for battery model number, battery ID, manufacturing date, shipping date, shipping destination ID, arrival date, and sales date. The battery model number field records the model number of battery 47. The battery ID field records the battery ID assigned to battery 47. The manufacturing date field records the manufacturing date of battery 47.

[0035] The shipping date field records the shipping date to the customer. The customer ID field records the customer ID. The arrival date field records the date the battery 47 arrived at the customer, more specifically the date it was placed in the customer's battery rack 40 and the battery ID was detected by the detector 42. The sale date field records the date the battery 47 was sold to the end user. The manufacturing DB 62 has one record for each battery ID.

[0036] Figure 5 is an explanatory diagram illustrating the record layout of the shelf inventory DB 61. The shelf inventory DB 61 is a database that records the storage status of batteries 47 in each position of the battery shelf 40 and associates this information with the batteries 47 that are stored there.

[0037] The shelf inventory DB61 has a location field, a status field, a battery ID field, a battery model number field, a receiving date and time field, and a shipping date and time field. The location field records the location ID assigned to each battery storage location in the battery shelf 40.

[0038] The status field records the battery 47's presence at each battery location. "Present" means that battery 47 is present, and "Empty" means that battery 47 is not present.

[0039] The Battery ID field records the Battery ID of the battery 47 that is stored. The Battery Model Number field records the model number of the battery 47 that is stored. The Arrival Date and Time field records the date and time when the battery 47 was stored in the battery shelf 40. The Shipment Date and Time field records the date and time when the battery 47 was removed from the battery shelf 40. "-" means that the battery 47 has not been removed. The shelf inventory DB 61 has one record for each battery storage location.

[0040] This explains the difference between the location of "P03" and the location of "P05," both of which have "empty" recorded in the status field. The battery 47 housed in "P03" was removed at the date and time recorded in the shipping date and time field, but it is unknown whether it was sold. The battery 47 may have been temporarily removed, for example, for a voltage check or to explain to a customer.

[0041] When battery 47, which had been temporarily removed, is returned to battery shelf 40, the data in the shipping date and time field is erased, and the status field is changed to "Yes". Furthermore, if a store employee or sales representative temporarily removes battery 47 from battery shelf 40, they should return it to the same battery storage location.

[0042] The "P05" position is either a location where a battery 47 has never been stored, or a battery 47 that was stored there has been sold and is therefore unlikely to be returned to the battery shelf 40. For this reason, the fields after the battery ID are blank. If the control unit 11 receives notification via the retailer's POS (Point of Sales) system or the like that a battery 47 stored in the P03 position has been sold, or if a predetermined time, such as one hour, has elapsed since the battery 47 was removed, the control unit 11 changes the fields after the battery ID in the P03 record to blank.

[0043] Figure 6 is a flowchart illustrating the program processing flow in the first information processing device 10. The control unit 11 executes the program in Figure 6 periodically, for example, every 30 minutes. The control unit 11 may also execute the program in Figure 6 when, for example, a smart sensor (not shown) detects that a person is approaching the battery shelf 40. The control unit 11 may continue to execute the program in Figure 6 repeatedly.

[0044] The control unit 11 reads the battery ID and model number from an ID tag 48 located near one of the detectors 42 (step S501). The control unit 11 determines whether the battery storage location corresponding to the ID tag 48 is empty or not (step S502). Specifically, if no readable ID tag 48 is detected in step S501, the control unit 11 determines that the corresponding battery storage location is empty.

[0045] If it is determined that the battery compartment is empty (YES in step S502), the control unit 21 starts the empty compartment processing subroutine (step S503). The empty compartment processing subroutine records information in the shelf inventory DB 61 when the battery compartment is empty. The processing flow of the empty compartment processing subroutine will be described later.

[0046] If it is determined that the battery is not empty (NO in step S502), the control unit 11 determines whether the battery ID read in step S501 is the same as the battery ID recorded in the battery ID field of the record for the corresponding battery storage location in the shelf inventory DB 61 (step S504). In the following description, the record determined in step S504 will be referred to as the record being processed.

[0047] If it is determined that they are the same (YES in step S504), the control unit 11 determines whether or not the shipping date and time is recorded in the shipping date and time field of the record being processed (step S505). If it is determined that the shipping date and time is recorded (YES in step S505), the control unit 11 erases the record of the shipping date and time (step S506).

[0048] If it is determined that they are not the same (NO in step S504), the control unit 11 determines whether or not a battery ID is recorded in the battery ID field of the record being processed (step S511). If it is determined that a battery ID is recorded (YES in step S511), the control unit 11 sends a sales notification to the server 20 indicating that the battery 47 corresponding to that battery ID has been sold (step S512). The sales notification includes sales information indicating that the battery 47 has been sold, the battery ID, and a shipping destination ID indicating the store where the first information processing device 10 is located. The sales information is an example of inbound / outbound information indicating the shipment of the battery 47.

[0049] If it is determined that the battery ID is not recorded (NO in step S511), or after the completion of step S512, the control unit 11 records information in the record being processed (step S513). Specifically, the control unit 11 records the battery ID and battery model number read in step S501 in the battery ID field and battery model number field, respectively. The control unit 11 records the date and time when step S501 was executed in the arrival date and time field. The control unit 11 records "-" in the shipping date and time field.

[0050] The control unit 11 sends an arrival notification to the server 20 indicating that the battery 47 corresponding to the battery ID read in step S501 has arrived (step S514). The arrival notification includes receiving and shipping information indicating the arrival of the battery 47, the battery ID, and the shipping destination ID indicating the retail store where the first information processing device 10 is located.

[0051] If it is determined that the shipping date and time have not been recorded (NO in step S505), after the completion of step S503, after the completion of step S506, or after the completion of step S514, the control unit 11 determines whether or not it has finished processing all detectors 42 (step S515). If it is determined that it has not finished (NO in step S515), the control unit 11 returns to step S501. If it is determined that it has finished (YES in step S515), the control unit 11 terminates the processing.

[0052] In addition, the control unit 11 does not need to transmit the shipping destination ID in steps S512 and S514. The server 20 can identify the source shipping destination ID based on the source information of the communication between the first information processing device 10 and the server 20.

[0053] Figure 7 is a flowchart illustrating the processing flow of the empty-location processing subroutine. The empty-location processing subroutine records information in the shelf inventory DB61 when the battery storage location is empty.

[0054] The control unit 11 extracts records from the shelf inventory DB 61 that are determined to be empty, and determines whether or not a battery ID is recorded in the battery ID field (step S521). In the following description, the record determined in step S521 will be referred to as the record being processed.

[0055] If it is determined that the battery ID is not recorded (NO in step S521), the control unit 11 terminates processing. If it is determined that the battery ID is recorded (YES in step S521), the control unit 11 determines whether or not the shipping date and time is recorded in the shipping date and time field of the record being processed (step S522). If it is determined that it is not recorded (NO in step S522), the control unit 11 records the date and time when step S501 was executed in the shipping date and time field (step S523). The control unit 11 terminates processing.

[0056] If it is determined that the record is recorded (YES in step S522), the control unit 11 determines whether the elapsed time from the time recorded in the shipping date and time field of the record being processed exceeds a predetermined threshold (step S525). The predetermined time is the upper limit for the time when the battery 47 is temporarily taken out of the battery shelf 40, and is determined according to the circumstances of each retailer. For example, a retailer that has equipment for supplemental charging of the battery 47 may set it to about a full day. A retailer that rarely takes batteries out temporarily may set it to about one hour.

[0057] If the control unit 11 determines that the predetermined time has not elapsed (NO in step S525), it terminates processing. If the control unit 11 determines that the predetermined time has elapsed (YES in step S525), it sends a sales notification to the server 20 indicating that the battery 47 corresponding to the battery ID has been sold (step S526). The sales notification includes sales information indicating that the battery 47 has been sold and the battery ID. The control unit 11 deletes the data from the battery ID field onward of the record being processed (step S527). The control unit 11 terminates processing.

[0058] Figure 8 is a flowchart illustrating the program's processing flow on server 20. The control unit 21 determines whether it has received the arrival notification sent in step S514 of the program described using Figure 6 (step S601). If it determines that it has received the notification (YES in step S601), the control unit 21 searches the manufacturing DB 62 using the battery ID included in the arrival notification as the key and updates the extracted record (step S602). Specifically, the control unit 21 records the shipping destination ID included in the arrival notification in the shipping destination field of the extracted record, and the date the arrival notification was sent or received in the arrival date field.

[0059] If it is determined that an arrival notification has not been received (NO in step S601), or after the completion of step S602, the control unit 21 determines whether or not it has received the sales notification sent in step S512 of the program described using Figure 6 or in step S526 of the subroutine described using Figure 7 (step S603).

[0060] If it is determined that the notification has been received (YES in step S603), the control unit 21 searches the manufacturing DB 62 using the battery ID included in the sales notification as the key and updates the extracted record (step S604). Specifically, the control unit 21 records the date the shipping notification was sent or received in the sales date field of the extracted record.

[0061] The control unit 21 sends a notification to the second information processing device 30 of the sales representative responsible for the sales store corresponding to the shipping destination ID of the extracted record, such as "Model number *** has been sold at sales store number *" (step S605). Email or SMS (Short Message Service) is used as the transmission means. The transmission means may also be a pop-up notification using application software installed on the second information processing device 30.

[0062] The control unit 21 may add information such as the number of batteries 47 of the same model number in stock at the sales store to the notification, based on the data recorded in the manufacturing DB 62. If it is determined that the notification has not been received (NO in step S603), or after the completion of step S605, the control unit 21 determines whether or not to terminate the process (step S606). For example, if the scheduled operating time of the server 20 has ended, the control unit 21 determines to terminate the process.

[0063] If it is determined that the process should not be terminated (NO in step S606), the control unit 21 returns to step S601. If it is determined that the process should be terminated (YES in step S606), the control unit 21 terminates the process.

[0064] Figure 9 is a flowchart illustrating the program's processing flow when a search request is received. When a user operates the touch panel 15 to initiate a search, the control unit 11 executes the program shown in Figure 9.

[0065] The control unit 11 receives search conditions such as the vehicle model or vehicle name specified by the user (step S541). The vehicle model or vehicle name is an example of information relating to the vehicle. The control unit 11 sends the search conditions to a web service or application software that responds with a suitable battery model number when the search conditions are entered, and obtains a response (step S542).

[0066] The control unit 11 determines whether each battery model number included in the response is in stock (step S543). Specifically, the control unit 11 searches the shelf inventory DB 61 using the battery model number included in the response as a key, and determines that there is no stock if no records are found, or if "None" is recorded in the status field of the extracted record.

[0067] The control unit 11 displays the battery model number acquired in step S542 and its respective inventory status on the touch panel 15 (step S544). The battery model number is an example of information that identifies the battery 47 suitable for the vehicle specified by the user. The inventory information is an example of information regarding whether or not the battery 47 corresponding to the battery model number is stored in the battery shelf 40. An example of the display will be described later. The control unit 11 determines whether or not the selection of the sales button 76 (see Figure 10) has been accepted (step S545).

[0068] If the control unit determines that the selection of the sales button 76 has been accepted (YES in step S545), the control unit 11 waits for the battery 47 with the battery model number corresponding to the selected sales button 76 to be taken out of the battery shelf 40 (step S546). Specifically, the control unit 11 searches the shelf inventory DB 61 using the battery model number as a key and extracts the location where the battery 47 of that model number is stored. The control unit 11 waits until the detector 42 corresponding to the extracted location does not detect the ID tag 48.

[0069] The control unit 11 sends a sales notification to the server 20 indicating that the battery 47 corresponding to the ID tag 48 that is no longer detected has been sold (step S547). The sales notification includes sales information indicating that the battery 47 has been sold and the battery ID. The control unit 11 extracts the record corresponding to the battery 47 from the shelf inventory DB 61 and deletes the data from the battery ID field onward (step S548).

[0070] If the control unit determines that the selection of the sales button 76 has not been accepted (NO in step S545), the control unit 11 determines whether or not the selection of the order button 77 (see Figure 10) has been accepted (step S551). If the control unit determines that the selection of the order button 77 has been accepted (YES in step S551), the control unit 11 sends a notification regarding the order of the battery 47 of the model number corresponding to the accepted order button 77 to the sales representative's second information processing device 30, either via the server 20 or directly (step S552).

[0071] The sales representative will promptly deliver the ordered battery model 47 to the retailer, if possible. If there are circumstances such as a stock shortage, the sales representative will take appropriate action, such as suggesting an alternative product or transferring the battery from another retailer that has it in stock.

[0072] If it is determined that the selection of the order button 77 has not been accepted (NO in step S551), after the completion of step S552 or step S548, the control unit 11 determines whether or not it has received a user's instruction to exit the results screen (step S553). If it is determined that it has not been accepted (NO in step S553), the control unit 11 returns to step S545. If it is determined that it has been accepted (YES in step S553), the control unit 11 terminates the process.

[0073] Figure 10 is an example screen. In step S544, which was explained using Figure 9, the control unit 11 displays the screen shown in Figure 10. The screen in Figure 10 displays the vehicle model field 71 and the search results field 72.

[0074] The vehicle model field 71 displays vehicle models extracted based on keywords entered by the user. Keywords are examples of vehicle information received from the user. The search results field 72 displays in a table format the types of batteries 47 that are compatible with the vehicle models displayed in the vehicle model field 71, the battery model numbers, and the stock status. A sales button 76 is displayed for batteries 47 that are "in stock," and an order button 77 is displayed for batteries 47 that are "out of stock." The sales button 76 and the order button 77 accept input from the user regarding sales or orders.

[0075] The string indicating the battery model number may be a link. If the user selects a link, the control unit 11 displays the detailed specifications of the battery 47 and related information such as the replacement procedure. If the user selects a link for a battery 47 that is "out of stock," the control unit 11 may display the delivery date and the stock status of nearby stores.

[0076] If multiple vehicle models are extracted based on keywords specified by the user, the control unit 11 will display each vehicle model and its corresponding battery. The control unit 11 may also display information that may be helpful to the user in identifying the vehicle model, such as a photograph of the vehicle's exterior, the vehicle name, and the sales period.

[0077] In the screen shown in Figure 10, the control unit 11 may display the location where the "In Stock" batteries 47 are located. Even in a large battery shelf 40, the user can quickly find the battery 47 they need. The control unit 11 may also illuminate the LED (Light Emitting Diode) provided on the shelf where the "In Stock" batteries 47 are located.

[0078] Furthermore, users may select the necessary batteries 47 themselves and take them out of the battery shelf 40 without operating the touch panel 15. Users with sufficient expertise do not need to spend time operating the touch panel 15. According to this embodiment, an inventory management system 50 can be provided that allows each user to proceed with their work in a manner that suits their level of knowledge.

[0079] According to this embodiment, an information processing method is provided that allows sales representatives to quickly replenish batteries 47 when they are sold. This prevents stockouts, thus preventing lost sales opportunities for retailers and providing an inventory management system 50 that also contributes to providing appropriate service to end users who visit the store.

[0080] Instead of automatically shipping the same model of battery 47 that was sold, a sales representative intervenes to make a decision, taking into account various information such as the release status of new battery models, automobile sales trends, and demographics in the trading area, so that the appropriate model of battery 47 can be placed on the battery shelf 40.

[0081] The model and sales date of each battery 47 sold at each retailer are stored in the manufacturing database 62. The data stored in the manufacturing database 62 is useful for future demand forecasting and production planning. Therefore, it is possible to provide an information processing method that contributes to improving the accuracy of demand forecasting and production planning for battery 47.

[0082] [Example 1] Figure 11 is an explanatory diagram illustrating a modified battery tray 40 and detector 42. In this modified example, the detector 42 is a camera positioned to photograph the front of the battery tray 40. The ID tag 48 is a one-dimensional or two-dimensional barcode placed on the front of the individual packaging box. The barcode records the battery ID and battery model number.

[0083] The control unit 11 analyzes the images captured by the detector 42 to read the battery ID, battery model number, and location from the barcodes placed on each individual packaging box, and records them in the shelf inventory DB 61. In other words, the control unit 11 and the detector 42 work together to perform the function of a barcode reader.

[0084] The control unit 11 may read the battery ID and battery model number from the individual packaging box by character recognition. According to this modified example, the information processing system of Embodiment 1 can be realized using a battery rack 40 that does not have an RFID reader.

[0085] The detector 42 may also be a barcode reader. Specifically, it is equipped with barcodes so that it can read barcodes placed on the front surface of each individual packaging box. The robot may automatically read the barcodes and transmit the location where the individual packaging boxes are housed and the barcode reading results to the first information processing device 10.

[0086] [Embodiment 2] This embodiment relates to an information processing method for notifying the time when supplemental charging is required. Parts common to Embodiment 1 will not be explained.

[0087] It is known that lead-acid batteries for automobiles can experience a voltage drop even when simply stored without being used. If a battery has been in stock at a retailer for a predetermined period, such as six months, it may be returned to the battery manufacturer for recharging. Since voltage drop is more likely to occur at higher storage temperatures, the predetermined period is determined based on retailers with higher storage temperatures.

[0088] The sales representative is also responsible for returning the battery 47 to the battery manufacturer for recharging. Since recharging incurs costs, it is desirable to determine the timing of recharging appropriately based on the storage environment of the retail store. However, determining and managing appropriate recharging intervals for each retail store is complicated and difficult to implement. The information processing method of this embodiment provides the sales representative with information on the appropriate timing for recharging.

[0089] Figure 12 is an explanatory diagram illustrating the record layout of the manufacturing DB 62 in Embodiment 2. The manufacturing DB 62 is a database that records the model number of the battery 47, the battery ID, the manufacturing date, the shipping date, the shipping destination ID uniquely assigned to the shipping destination, the arrival date at the shipping destination, the sales date, and the charging information in association with each other.

[0090] The manufacturing DB62 has a battery model number field, a battery ID field, a manufacturing date field, a shipping date field, a shipping destination ID field, an arrival date field, a sales date field, and a charging information field. Except for the charging information field, it is the same as the manufacturing DB62 of Embodiment 1 described using Figure 4, so the description is omitted.

[0091] The charging information field includes a start date field, an environment field, and an estimated remaining capacity field. The environment field includes a spring / autumn field, a summer field, and a winter field. The environment field may also have twelve subfields, from January to December. In addition, the environment field may have subfields divided into arbitrary time periods.

[0092] The "Start Date" field records the start date for calculating the remaining capacity of battery 47. The start date is the most recent of the battery 47's manufacturing date and the date of recharging. Each subfield in the "Environment" field records the typical temperature for each period in the environment in which battery 47 is stored. Sales representatives check the storage conditions at their assigned dealerships and enter values ​​in the respective subfields. The "Estimated Remaining Capacity" field records the estimated remaining capacity of each battery 47. The estimated remaining capacity on the start date is 100 percent.

[0093] This section outlines the method for estimating the remaining capacity. The following explanation uses the example of calculating the remaining capacity on a monthly basis. The estimated remaining capacity Ka of battery 47 with a remaining capacity of K0, when stored for one month in an environment at temperature T, can be expressed by equation (1). Ka = f(T)·K0 ... (1) f(T) represents the coefficient related to capacity degradation.

[0094] Similarly, the estimated remaining capacity Kb of battery 47 with remaining capacity K0, when stored for one month in an environment at temperature T1 and then for one month in an environment at temperature T2, can be expressed by equation (2). Kb =f(T2) f(T1) K0 ‥‥‥ (2) In this way, by multiplying by a coefficient f(T) determined for each temperature T, the remaining capacity after any number of months can be calculated. Note that f(T) is determined based on experiments or theory regarding the voltage drop of the battery 47. f(T) is a function that decreases monotonically with increasing temperature T and is recorded in the auxiliary storage device 23 in any format such as a numerical table or approximation formula.

[0095] Figure 13 is a flowchart illustrating the processing flow of the program in Embodiment 2. The program shown in Figure 13 is executed periodically by the control unit 21. The control unit 21 executes the program in Figure 13 every month from the start date for each battery 47 recorded in the manufacturing DB 62.

[0096] The control unit 21 extracts the record to be processed, which is a record relating to the battery 47 to be calculated, from the manufacturing DB 62, and obtains the temperature T, which is the storage environment, from the environment subfield corresponding to the time of calculation (step S621). The control unit 21 obtains the coefficient f(T) based on a numerical table or approximation formula, etc., recorded in the auxiliary storage device 23 (step S622).

[0097] The control unit 21 obtains the previously calculated estimated remaining capacity K0 from the estimated remaining capacity field of the record to be processed (step S623). The control unit 21 calculates a new estimated value of the remaining capacity Ka based on equation (1) and updates the data recorded in the estimated remaining capacity field (step S624).

[0098] The control unit 21 determines whether the new remaining capacity Ka falls below a threshold for determining whether supplemental charging is necessary (step S625). The threshold is defined as a value such as 80 percent or 85 percent. A sales representative may define the threshold for each retailer and for each battery model.

[0099] If it is determined that the threshold has been exceeded (YES in step S625), the control unit 21 sends a notification to the second information processing device 30 of the sales representative in charge of the sales store corresponding to the shipping destination ID of the record to be processed, such as "The remaining capacity of battery ID ***, model number *** in stock at sales store number * has fallen below ** percent." (step S626).

[0100] If it is determined that the remaining capacity does not fall below the threshold (NO in step S625), or after the completion of step S626, the control unit 21 determines whether the processing of the battery 47 for which the estimated remaining capacity should be updated has been completed (step S627). If it is determined that it has not been completed (NO in step S627), the control unit 21 returns to step S621. If it is determined that it has been completed (YES in step S627), the control unit 21 terminates the process.

[0101] If the retailer has equipment for supplemental charging, the sales representative may contact the retailer's engineer or other relevant personnel with the battery ID of the battery 47 that requires supplemental charging. Alternatively, the control unit 21 may directly notify the retailer's engineer or other relevant personnel of the need for supplemental charging in step S626.

[0102] According to this embodiment, an inventory management system 50 can be provided that alerts sales representatives to batteries 47 that require recharging. Sales representatives replace batteries 47 that require recharging with replacement batteries of the same model number. Sales representatives may also collect batteries 47 that require recharging and return them to the original retailer after recharging is complete. Since batteries 47 that require recharging are batteries 47 that have remained unsold for a long period of time, sales representatives may review the batteries 47 placed on the battery shelves 40 and replace them with batteries 47 of a new model number.

[0103] The coefficient f(T) may be defined for any period of time, such as two months, one week, one day, or one hour.

[0104] [Differentiation 2] If the coefficient f(T) is defined for a short period, the control unit 21 may sequentially update the estimated remaining capacity based on the measured temperature T. For example, the control unit 21 can update the estimated remaining capacity in real time by sequentially receiving the temperature T from a smart sensor-type thermometer attached to the battery shelf 40. Even if the storage temperature of the batteries 47 fluctuates unexpectedly due to the effects of abnormal weather, an inventory management system 50 can be provided that appropriately calculates the estimated remaining capacity based on the measured value.

[0105] According to this modified example, an inventory management system 50 can be provided that accurately determines whether or not supplemental charging is necessary without the need to take the time and effort of actually measuring the output voltage of the battery 47 or the specific gravity of the electrolyte.

[0106] [Difference 3] A smart sensor-type thermometer may be placed in the cargo compartment of the transport vehicle that carries the batteries 47 from the manufacturer to the retailer. The control unit 21 can calculate the estimated discharge amount during transport based on the temperature of the cargo compartment, i.e., the transport temperature, and the transport time. For example, if the batteries 47 are transported in a transport vehicle without air conditioning in the cargo compartment during the summer, the batteries 47 will become hot, which is likely to cause a decrease in remaining capacity. By determining whether or not supplemental charging is necessary, including such a decrease in remaining capacity during transport, an inventory management system 50 can be provided that can appropriately manage the quality of the batteries 47 sold to end users.

[0107] [Differentiation Example 4] The charging information field is provided in the manufacturing DB62 as described using Figure 4, and the program as described using Figure 13 may be executed by the control unit 11. This provides an inventory management system 50 that reduces the load on the server 20 and the communication load.

[0108] [Embodiment 3] This embodiment relates to an inventory management system 50 that can input information regarding supplemental charging and replacement from a first information processing device 10 located in a retail store. Parts common to Embodiment 1 will not be described.

[0109] Figure 14 shows an example screen of Embodiment 3. When the control unit 11 receives a display instruction from the user, it displays the screen shown in Figure 14 on the touch panel 15 based on the shelf inventory DB 61. The screen shown in Figure 14 schematically displays the battery shelf 40 shown in Figure 3 as viewed from the front. That is, the state in which two batteries 47 are housed in each of the three shelves is schematically shown by rectangular frames arranged in three rows and two columns.

[0110] The model number of each battery 47 is displayed in large letters inside the rectangular frame. The "-" in the rectangular frame in the lower left indicates that it is empty. The dashed frame and italicized model number in the center left indicates that battery 47 has been removed. In other words, the screen in Figure 14 illustrates the arrangement of batteries 47 in the battery shelf 40.

[0111] Below each model number, a sales button 76, a supplemental charging button 78, and a replacement button 79 are arranged in a row. The sales button 76 is the same as the sales button 76 of Embodiment 1 described using Figure 10, so its description is omitted.

[0112] A user, such as an engineer at a sales outlet, measures the voltage or specific gravity of the electrolyte in the battery 47 and selects the supplemental charge button 78 if they determine that the remaining capacity is low. Upon receiving the selection of the supplemental charge button 78, the control unit 11 sends information to the server 20 indicating that supplemental charging is necessary. The server 20 then notifies the sales representative's second information processing device 30 that supplemental charging is necessary.

[0113] For example, if an old battery 47 is replaced with a new battery 47, the user selects the replacement button 79. Upon receiving the selection of the replacement button 79, the control unit 11 reads the battery ID and battery model number via the detector 42 and updates the shelf inventory DB 61. The control unit 11 updates the display screen based on the shelf inventory DB 61, and the model number on the screen is also updated. The control unit 11 sends information about the inventory change to the server 20. The control unit 21 updates the manufacturing DB 62. The old battery 47 is collected by a sales representative and returned to the manufacturer.

[0114] Figure 15 is a flowchart illustrating the program processing flow in the first information processing device 10 of Embodiment 3. The control unit 11 displays the screen described using Figure 14 on the touch panel 15 based on the shelf inventory DB 61 (step S561). The control unit 11 determines whether or not the selection of the sales button 76 has been accepted (step S562).

[0115] If the control unit determines that the selection of the sales button 76 has been accepted (YES in step S562), the control unit 11 waits for the battery 47, which is housed in the battery storage position corresponding to the selected sales button 76, to be removed from the battery shelf 40 (step S563). Specifically, the control unit 11 waits until the detector 42 corresponding to the selected sales button 76 no longer detects the ID tag 48.

[0116] The control unit 11 sends a sales notification to the server 20 indicating that the battery 47 corresponding to the ID tag 48 that is no longer detected has been sold (step S564). The sales notification includes the battery ID. The control unit 11 extracts the record corresponding to the battery 47 from the shelf inventory DB 61 and deletes the data from the battery ID field onward (step S565).

[0117] If the control unit determines that the selection of the sales button 76 has not been accepted (NO in step S562), the control unit 11 determines whether or not the selection of the supplemental charge button 78 has been accepted (step S566). If the control unit determines that the selection of the supplemental charge button 78 has been accepted (YES in step S566), the control unit 11 sends a supplemental charge notification to the control unit 21 indicating to the server 20 that the user is requesting supplemental charging (step S567). The supplemental charge notification includes the battery ID of the battery 47 for which supplemental charging is being requested.

[0118] If the control unit determines that the selection of the supplemental charge button 78 has not been accepted (NO in step S566), it determines whether the selection of the replacement button 79 has been accepted (step S571). If it determines that the selection of the replacement button 79 has been accepted (YES in step S571), the control unit 11 operates the detector 42 corresponding to the selected replacement button 79 and reads the battery ID and battery model number from the ID tag 48 (step S572).

[0119] The control unit 11 extracts a record from the shelf inventory DB 61 corresponding to the battery storage location for which the replacement button 79 was selected. The control unit 11 updates the data recorded in the extracted record (step S573).

[0120] Specifically, the control unit 11 temporarily stores the battery ID and battery model number recorded in the extracted record in the auxiliary storage device 13 or the main storage device 12. The control unit 11 records "Yes" in the status field of the extracted record, and the information read in step S572 in the battery ID field and battery model number field, respectively. The control unit 11 records the date and time when the selection of the replacement button 79 was received in the arrival date and time field. The control unit 11 records "-" in the shipping date and time field.

[0121] The control unit 11 sends a replacement notification to the server 20 via the control unit 21 indicating that a battery 47 housed in the battery tray 40 has been replaced (step S574). The replacement notification includes the location of the battery storage area where the battery 47 was replaced and the battery IDs of the battery 47 before and after the replacement.

[0122] If the control unit determines that it has not accepted the selection of the exchange button 79 (NO in step S571), or after the completion of step S565, step S567, or step S574, the control unit 11 determines whether or not to terminate the process (step S575). For example, if the user instructs the end of the screen display as described using Figure 14, the control unit 11 determines to terminate the process.

[0123] If it is determined that the process should not be terminated (NO in step S575), the control unit 11 returns to step S561. If it is determined that the process should be terminated (YES in step S575), the control unit 11 terminates the process.

[0124] Figure 16 is a flowchart illustrating the program processing flow in the server 20 of Embodiment 3. The control unit 21 determines whether or not it has received the sales notification sent in step S564 of the program described using Figure 15 (step S641).

[0125] If it is determined that the notification has been received (YES in step S641), the control unit 21 searches the manufacturing DB 62 using the battery ID included in the sales notification as the key and updates the extracted record (step S642). Specifically, the control unit 21 records the date the sales notification was sent or received in the sales date field of the extracted record.

[0126] The control unit 21 sends a notification to the second information processing device 30 of the sales representative in charge of the sales store that sent the sales notification, such as "Model number *** has been sold at sales store number *" (step S643).

[0127] If it is determined that the sales notification has not been received (NO in step S641), or after the completion of step S643, the control unit 21 determines whether or not it has received the supplemental charge notification sent in step S567 of the program described using Figure 15 (step S644).

[0128] If the control unit determines that it has received the notification (YES in step S644), the control unit 21 sends a notification to the second information processing device 30 of the sales representative in charge of the sales store that sent the supplemental charge notification, such as "Supplemental charging of battery ID ***, model number *** has been requested from the * sales store" (step S645).

[0129] If it is determined that no supplemental charging notification has been received (NO in step S644), or after the completion of step S645, the control unit 21 determines whether or not it has received the replacement notification sent in step S574 of the program described using Figure 15 (step S646).

[0130] If it determines that the notification has been received (YES in step S646), the control unit 21 searches the manufacturing DB 62 using the replacement battery ID included in the replacement notification as the key and updates the extracted record (step S647). Specifically, the control unit 21 records the shipping destination ID corresponding to the retailer that sent the replacement notification in the shipping destination field of the record extracted corresponding to the battery ID, and the date the replacement notification was sent or received on the arrival date, respectively.

[0131] For batteries 47 that are not yet replaced, the control unit 21 updates the manufacturing DB 62 according to how the battery 47 is being handled. For example, if the battery is to be discarded, the control unit 21 sets a flag in the record corresponding to the battery 47 to indicate that it has been discarded. If the battery is to be stored in the manufacturer's warehouse, the control unit 21 changes the shipping destination ID in the record corresponding to the battery 47 to an ID indicating the warehouse where it is being stored.

[0132] If it is determined that no exchange notification has been received (NO in step S646), or after the completion of step S647, the control unit 21 determines whether or not to terminate the process (step S648). For example, if the scheduled operating time of the server 20 has ended, the control unit 21 determines to terminate the process.

[0133] If it is determined that the process should not be terminated (NO in step S648), the control unit 21 returns to step S641. If it is determined that the process should be terminated (YES in step S648), the control unit 21 terminates the process.

[0134] According to this embodiment, an inventory management system 50 can be provided that allows for the input of information regarding supplemental charging and replacement from a first information processing device 10 located at a dealership. Dealership staff can communicate requests more easily and accurately than by using telephone or email.

[0135] [Embodiment 4] This embodiment relates to an inventory management system 50 having a function for aggregating data recorded in a manufacturing database 62. Parts common to Embodiment 1 will not be described.

[0136] Manufacturers develop medium- to long-term sales plans for their products and create production plans based on these plans to avoid stockouts and excessive inventory. For example, sales plans include weekly or monthly sales quantities for each product. Similarly, production plans include weekly or monthly production quantities for each product.

[0137] If sales significantly exceed the sales plan, or if manufacturing significantly falls short of the production plan, there is a risk of product shortages. If sales significantly fall short of the sales plan, or if manufacturing significantly exceeds the production plan, there is a risk of excessive inventory.

[0138] By detecting such discrepancies between planned and actual values—that is, large differences between planned and actual values—at an early stage and revising the plan, it is possible to avoid the risk of lost sales opportunities due to stockouts and the risk of profit pressure due to excessive inventory. In this embodiment, a program that detects the occurrence of a discrepancy and notifies relevant parties will be described.

[0139] Figure 17 is a flowchart illustrating the processing flow of the program in Embodiment 4. The control unit 21 aggregates the manufacturing DB 62 to create monthly and weekly manufacturing performance data and sales performance data for each product (step S661).

[0140] The manufactured batteries 47 are recorded in the manufacturing database 62. Therefore, the manufacturing record can be calculated by counting the number of records recorded in the manufacturing database 62 for each battery model and sales month or sales week. The date of sale is recorded in the sales date field of the manufacturing database 62 for the sold batteries 47. Therefore, the sales record can be calculated by counting the number of records in the sales date field of the manufacturing database 62 for each battery model and sales month or sales week.

[0141] For aggregation, the functions of a general-purpose spreadsheet software may be used. The control unit 21 may input the manufacturing DB 62, a sample of output data, and prompts including natural language instructions such as "Use this data to create weekly and monthly sales performance data and manufacturing performance data in the format shown in the sample," to the generating AI and obtain the sales performance data and manufacturing performance data generated by the generating AI.

[0142] The control unit 21 calculates the discrepancy between the pre-created sales plan and manufacturing plan and the actual data compiled in step S661 (step S662). The control unit 21 determines whether the discrepancy is greater than a predetermined threshold (step S663).

[0143] If the control unit determines that the discrepancy is greater than the threshold (YES in step S663), the control unit 21 sends a notification regarding the discrepancy between actual results and the plan to a second information processing device 30 used by relevant parties such as the head of the sales department and the head of the manufacturing department (step S664). For example, "Sales results for battery model *** in November exceeded the sales plan by 40 percent. Manufacturing results are in line with the manufacturing plan. Please refer to *** if you need more detailed data."

[0144] If the control unit 21 determines that the deviation is below the threshold (NO in step S663), or after the completion of step S664, the control unit 21 terminates the process.

[0145] According to this embodiment, an inventory management system 50 is provided that automatically aggregates sales performance data reflecting sales notifications sent sequentially from retailers and notifies the user if there is a discrepancy with the plan.

[0146] [Embodiment 5] Figure 18 is an explanatory diagram illustrating the configuration of the inventory management system 50 of Embodiment 5. This embodiment relates to a configuration in which the inventory management system 50 is realized by operating a general-purpose server computer 90 in combination with a program 97. Parts common to Embodiment 1 will not be explained.

[0147] The server computer 90 includes the aforementioned control unit 21, main memory 22, auxiliary memory 23, communication unit 24, and bus, as well as a read unit 29.

[0148] Program 97 is recorded on a portable recording medium 96. The control unit 21 reads Program 97 via the reading unit 29 and saves it to the auxiliary storage device 23. The control unit 21 may also read Program 97 stored in a semiconductor memory 98, such as flash memory, implemented in the server computer 90. Furthermore, the control unit 21 may download Program 97 from another computer (not shown) connected via the communication unit 24 and a network (not shown) and save it to the auxiliary storage device 23.

[0149] Program 97 is installed as a control program for the server computer 90, loaded into the main memory 22, and executed. The control unit 21 transmits the portion of Program 97 that is executed by the first information processing unit 10 and the portion that is executed by the second information processing unit 30 to their respective hardware.

[0150] The control unit 11 saves the received program 97 to the auxiliary storage device 13. The program 97 is installed as the control program for the first information processing device 10, loaded into the main memory 22, and executed.

[0151] The control unit of the second information processing device 30 also saves the received program 97 to the auxiliary storage device. The program 97 is installed as the control program of the second information processing device 30, loaded into the main memory, and executed. Thus, the inventory management system 50 described in Embodiment 1 is realized.

[0152] The inventory management system 50 described in Embodiment 1 is thus realized. The program 97 in this embodiment is an example of a program product. The program may be provided on a recording medium or distributed from an external computer. Computer programs can be deployed to run on a single computer, at a single site, or distributed across multiple sites and interconnected by a communication network.

[0153] The technical features (constituent elements) described in each embodiment are combinable with each other, and by combining them, new technical features can be formed. The embodiments disclosed herein should be considered in all respects to be illustrative and not restrictive. The scope of the present invention is indicated by the claims, not in the sense described above, and all modifications within the sense and scope equivalent to the claims are intended to be included.

[0154] The independent and dependent claims described in the claims can be combined with each other in any combination, regardless of the form of reference. Furthermore, while the claims use a multi-claim format in which claims refer to two or more other claims (multi-claim format), this is not the only option. Claims may also be described using a multi-claim format in which at least one multi-claim is referenced (multi-multi-claim format). [Explanation of Symbols]

[0155] 10 First Information Processing Device 11 Control Unit (First Control Unit) 12 Main storage 13 Auxiliary storage device 14 Communications Department 15 Touch panel 151 Display section 152 Input section 20 servers 21 Control Unit (Second Control Unit) 22 Main storage 23 Auxiliary storage device 24 Communications Department 29 Reading section 30. Second Information Processing Device 40 Battery shelves 42 detectors 47 Battery (lead acid battery) 48 ID tags 50 Inventory Management System 61 Shelf Inventory Database 62 Manufacturing DB 71 Vehicle Model Column 72 Search Results 76 Sales button 77 Order button 78. Recharge button 79 Replacement Button 90 Server Computers 96 Portable recording media 97 Programs 98 Semiconductor memory

Claims

1. An information processing method in which a first information processing device and a server connected to the first information processing device via a network operate in cooperation, The first information processing device is The system obtains inbound and outbound information that identifies the arrival of lead-acid batteries into battery shelves installed at retail stores and the shipment of lead-acid batteries from said battery shelves, and a battery ID (Identifier) ​​that identifies the lead-acid batteries related to the inbound and outbound information. The battery ID, the retailer ID identifying the retailer, and the inbound / outbound information are associated and transmitted to the server. The server records the received battery ID, the retailer ID, and the inbound / outbound information in the manufacturing database, associating them with each other. Information processing methods.

2. The battery ID is read from the lead-acid battery or the container in which the lead-acid battery is housed using RFID (Radio Frequency Identification), a barcode reader, or a camera. The information processing method according to claim 1.

3. The first information processing device, which includes a display unit, is located in the battery tray. The first information processing device displays the status of the lead-acid batteries being stored in the battery rack on the display unit based on the incoming and outgoing information. The information processing method according to claim 1.

4. The first information processing device is We accept input regarding vehicle information. Based on the information received about the vehicle, the vehicle model will be identified. The display unit will show information identifying the battery model number that matches the specified vehicle model, and information regarding whether or not a lead-acid battery corresponding to the battery model number is stored in the battery shelf. The information processing method according to claim 3.

5. The first information processing device or the server is The starting date for the remaining capacity of the aforementioned lead-acid battery is obtained, Based on the aforementioned start date and the storage temperature of the lead-acid battery, the remaining capacity of the lead-acid battery is calculated. If the calculated remaining capacity falls below a predetermined threshold, a notification is sent to the second information processing device connected to the server via the network. The information processing method according to claim 1.

6. The first information processing device or the server is The starting date for the remaining capacity of the aforementioned lead-acid battery is obtained, Based on the aforementioned start date, the transportation time and temperature until the lead-acid battery arrives at the battery shelf, and the storage temperature of the lead-acid battery, the remaining capacity of the lead-acid battery is calculated. If the calculated remaining capacity falls below a predetermined threshold, a notification is sent to the second information processing device connected to the server via the network. The information processing method according to claim 1.

7. The first information processing device is The battery ID and the date and time of shipment in which the shipment of the lead-acid battery was detected are recorded in association with each other. If no incoming lead-acid battery with the same battery ID as a lead-acid battery whose shipment has been detected has been detected, and the elapsed time since the shipment date exceeds a predetermined threshold, the battery ID and sales information indicating that the lead-acid battery with the battery ID has been sold are associated and sent to the server. If an incoming lead-acid battery with the same battery ID as a lead-acid battery that was previously detected as having been shipped is detected, the record of the shipping date and time will be deleted. The information processing method according to claim 1.

8. The aforementioned server, Based on the received battery ID and the sales information, the manufacturing database records that the battery corresponding to the battery ID has been sold. Based on the information on manufactured batteries recorded in the aforementioned manufacturing database, the actual values ​​regarding the quantity of lead-acid batteries manufactured are compiled. Based on the information on sold batteries recorded in the aforementioned manufacturing database, the actual manufacturing quantity of the lead-acid batteries is compiled. If the difference between the actual values ​​for the aggregated manufacturing quantity and sales quantity and the planned values ​​for the manufacturing quantity and sales quantity of the lead-acid battery exceeds a predetermined threshold, a notification is sent to the second information processing device connected to the server via the network. The information processing method according to claim 7.

9. The first information processing device is The input relating to the sale or recharging of the aforementioned lead-acid battery is received in association with a battery ID that identifies the aforementioned lead-acid battery. The received sales or supplemental charging input is associated with the battery ID and transmitted to the server. The information processing method according to claim 1.

10. The first information processing device is The input regarding the replacement of the lead-acid battery is received in association with a battery ID that identifies the lead-acid battery. The input received regarding the replacement of the lead-acid battery is transmitted to the server in association with the battery ID. The information processing method according to claim 1.

11. An information processing system including a first information processing device and a server connected to the first information processing device via a network, The first information processing device has a first control unit, The aforementioned server has a second control unit, The first control unit is, The system acquires inbound and outbound information that identifies the arrival of lead-acid batteries into battery shelves installed at retail stores and the shipment of lead-acid batteries from said battery shelves, and a battery ID that identifies the lead-acid batteries related to the inbound and outbound information. The battery ID, the retailer ID identifying the retailer, and the inbound / outbound information are associated and transmitted to the server. The second control unit associates the received battery ID, the retailer ID, and the inbound / outbound information and records them in the manufacturing database. Information processing system.

12. An information processing device comprising a control unit, The control unit, The system acquires inbound and outbound information that identifies the arrival of lead-acid batteries into battery shelves installed at retail stores and the shipment of lead-acid batteries from said battery shelves, and a battery ID that identifies the lead-acid batteries related to the inbound and outbound information. The battery ID, the retailer ID that identifies the retailer, and the inbound / outbound information are transmitted in association. Information processing device.

Images