JP4376676B2 - Parts management program - Google Patents

Description

  The present invention relates to a parts management program for managing information related to parts in a parts warehouse or a maintenance shop.

As is well known, electronic tags are being used to manage the number of parts in facilities such as parts warehouses and maintenance shops. In such a facility, a gate device for reading information from the electronic tag is installed, and when the electronic tag passes near the antenna of the gate device, the information of the electronic tag is read by the gate device, and the parts The number is increased or decreased.
Japanese Patent Laid-Open No. 2001-213502

  The conventional system comprising the gate device and the electronic tag described above is merely for managing the number of parts. Therefore, according to such a conventional system, it is not possible to manage whether the number of parts is reduced by taking parts out for sale or whether the number of parts is increased because parts are brought in for return. It was. In other words, the conventional system cannot manage sales based on the number of parts sold or the number of returned goods.

  The present invention has been made in view of the above-described conventional circumstances, and a parts management program for causing a computer to function as a device that enables management of sales of parts in a facility such as a parts warehouse or a maintenance factory. Is to provide.

The parts management program invented to solve the above-described problems is that the computer is a part from an electronic tag attached to the part via an electronic tag reader installed at the entrance and exit of the facility. The tag information reading means for reading the vehicle information including the information indicating the vehicle user and the vehicle information from the electronic tag attached to the vehicle, and the tag information reading means Based on the part information and the vehicle information, the entry / exit determination means for determining whether the part has been carried out by the vehicle or the carry-in, and when the entry / exit determination means has determined that the part has been carried out, When the vehicle information is information indicating the customer's vehicle, the number of parts is recorded in the storage device as the number of sales, and the entry / exit determination In the case but it is determined that the component is carried, when the vehicle information indicates a customer of the vehicle, that function as recorded means for recording in the storage device the number of the part as return number, characterized It is said.

  With this configuration, the number of parts loaded on the vehicle and carried out of the facility is counted as the number of sales, and the number of parts loaded on the vehicle and carried into the facility is counted as the number of returned goods. . Therefore, if the number obtained by subtracting the number of returned goods from the number of sales is multiplied by the price of the part, the sales of the part can be easily calculated.

  As described above, according to the present invention, sales of parts can be managed in a facility such as a parts warehouse or a maintenance factory.

  DESCRIPTION OF EMBODIMENTS Hereinafter, embodiments for carrying out the present invention will be described with reference to the accompanying drawings.

  FIG. 1 is a schematic diagram of a parts management system according to an embodiment of the present invention. The parts management system includes a parts warehouse gate device 10, a maintenance shop gate device 20, and a parts management server device 30, and these devices 10 to 30 are connected to each other via a network N. The network N is also connected to a database device 40 of another system described later.

  The parts warehouse gate apparatus 10 is an apparatus for managing the delivery of parts to or from the parts warehouse. The parts warehouse gate device 10 includes a pair of gate antennas 11 and 12 and a personal computer 13.

  The pair of gate antennas 11 and 12 are devices for exchanging radio waves with the electronic tag. Specifically, each of the gate antennas 11 and 12 is a metal bar formed in a U shape and has the same size. The passage port partitioned by the gate antennas 11 and 12 and the floor on which these are erected is arranged in parallel with the carry-in / out port provided only in the parts warehouse outside the parts warehouse. Has been placed. Accordingly, the parts and the vehicle loaded with the parts always go under the gate antennas 11 and 12 when passing through the carry-in / out port of the parts warehouse. In the present embodiment, the second gate antenna 12 is disposed on the side close to the parts warehouse, and the first gate antenna 11 is disposed on the outside thereof.

  The personal computer 13 is a device for managing the passage of the electronic tag using the gate antennas 11 and 12. FIG. 2 is a configuration diagram of the personal computer 13. The personal computer 13 includes a CPU [Central Processing Unit] 13a, a RAM [Random Access Memory] 13b, a display device 13c, an input device 13d, a communication adapter 13e, an electronic tag reader 13f, an FDD [Flexible Disk Drive] 13g, and a CDD [Compact Disk Drive] 13h and HDD [Hard Disk Drive] 13i.

  The CPU 13a is a central processing unit for controlling the personal computer 13 as a whole. The RAM 13b is a main storage device in which a work area is developed when the CPU 13a executes various programs. The display device 13c is a device for displaying various screens based on the screen data generated by the CPU 13a, and is specifically a liquid crystal display or a cathode ray tube display. The input device 13d is a device for receiving an input from an operator, and specifically a keyboard, a mouse, or a touch screen.

  The communication adapter 13e is a device for transmitting and receiving data to and from a router on the network N, and specifically, a LAN [Local Area Network] connection board, a terminal adapter, a modem, and the like. The electronic tag reader 13f is a device for outputting radio waves from the gate antennas 11 and 12 and receiving data from the electronic tag via the gate antennas 11 and 12.

  The FDD 13g and the CDD 13h are auxiliary storage devices for reading and writing data and programs from a computer-readable medium such as a flexible disk or a compact disk, and include a mechanism for detachably mounting the disk. Yes. The HDD 13i is an auxiliary storage device that is built in or externally attached to the personal computer 13, and stores various programs that are read and executed on the RAM 13b by the CPU 13a, and tables that are used when executing the various programs. Yes.

  Specifically, in the HDD 13i, in addition to an OS [Operating System] program for managing hardware and software in an integrated manner, a passing part journal table 14, a passing vehicle journal table 15, and an electronic tag monitoring program 16. A parts warehouse program 17 is installed.

  The passing parts journal table 14 is a table for recording information related to parts that have passed through the passing ports of the gate antennas 11 and 12. FIG. 3 is a diagram illustrating an example of the data structure of the passing part journal table 14. The records in the passing part journal table 14 of FIG. 3 have fields of “part ID”, “number”, “passing gate”, and “passing date / time”.

  Here, the “component ID” is a field in which the component ID stored in the electronic tag attached to the component is recorded. The component ID is identification information uniquely assigned to each component in order to identify the type of component. The “number” is a field in which the number of electronic tags when electronic tags storing the same component ID pass through the passage openings of the gate antennas 11 and 12 at the same time is recorded.

  Further, the “pass gate” is a field in which pass gate information indicating which of the first gate antenna 11 and the second gate antenna 12 has been hidden has been recorded. In this “passing gate” field, “outside” is recorded as information indicating that the part to which the electronic tag is attached has passed through the first gate antenna 11, and the part to which the electronic tag is attached is the second gate. “Inside” is recorded as information indicating that the antenna 12 has passed. The “passing date / time” is a field in which the year / month / day / hour / minute / second when the electronic tag affixed to the component has passed through the gate antennas 11 and 12 is recorded as passing date / time information.

  The passing vehicle journal table 15 is a table for recording information related to vehicles that have passed through the passing ports of the gate antennas 11 and 12. FIG. 4 is a diagram showing an example of the data structure of the passing vehicle journal table 15. The record in the passing vehicle journal table 15 of FIG. 4 has fields of “vehicle ID”, “passing gate”, and “passing date / time”.

  Here, the “vehicle ID” is a field in which the vehicle ID stored in the electronic tag attached to the vehicle is recorded. The vehicle ID is identification information uniquely assigned to each vehicle in order to identify the user of the vehicle. Vehicles include trucks and sales vehicles used by the above companies, forklifts used on the premises of parts warehouses and maintenance factories, sales of parts suppliers who supply parts to parts warehouses, and maintenance shops There is a customer's vehicle that is entrusted for maintenance.

  Further, the “pass gate” is a field in which pass gate information indicating which of the first gate antenna 11 and the second gate antenna 12 the vehicle on which the electronic tag is attached has been recorded is recorded. The “passing date / time” is a field in which the year / month / day / hour / minute / second when the electronic tag affixed to the vehicle has passed through the gate antennas 11 and 12 is recorded as passing date / time information.

  The electronic tag monitoring program 16 is a program for adding a function of detecting passage of an electronic tag using the gate antennas 11 and 12 to a personal computer. Details of processing executed by the CPU 13a in accordance with the electronic tag monitoring program 16 will be described later.

  The parts warehouse program 17 is a program for adding a function for managing information on parts or vehicles that have passed through the gate antennas 11 and 12 to the personal computer. The contents of processing executed by the CPU 13a according to the parts warehouse program 17 will be described later.

  The maintenance factory gate device 20 is an apparatus for managing the delivery of goods to or from the maintenance factory. The maintenance shop gate apparatus 20 includes a pair of gate antennas 21 and 22 and a personal computer 23.

  The pair of gate antennas 21 and 22 are the same as the pair of gate antennas 11 and 12 of the component warehouse gate device 10 described above. In addition, the passage openings by the gate antennas 21 and 22 are arranged on the outside of the maintenance factory so as to be arranged in parallel with a carry-in / out opening provided only in the maintenance factory. Therefore, the parts and the vehicle loaded with the parts always go under the gate antennas 21 and 22 when passing through the carry-in / out port of the parts warehouse. In the present embodiment, the second gate antenna 22 is disposed on the side close to the parts warehouse, and the first gate antenna 21 is disposed on the outside thereof.

  The personal computer 23 is a device for managing the passage of the electronic tag using the gate antennas 21 and 22. FIG. 5 is a configuration diagram of the personal computer 23. The personal computer 23 includes the same hardware 23a to 23i as the hardware 13a to 13i of the personal computer 13 of the parts warehouse gate device 10 described above.

  In addition to the OS program, the passing part journal table 24, the passing vehicle journal table 25, the electronic tag monitoring program 26, and the maintenance factory program 27 are installed in the HDD 23i. The passing parts journal table 24, the passing vehicle journal table 25, and the electronic tag monitoring program 26 are the same as those of the parts warehouse gate device 10 described above.

  The maintenance shop program 27 is a program for adding a function of managing information on parts or vehicles that have passed through the gate antennas 21 and 22 to the personal computer. The contents of the process executed by the CPU 23a according to the maintenance factory program 27 will be described later.

  The parts management server device 30 is a device for managing information on parts and vehicles to which electronic tags are attached. FIG. 6 is a configuration diagram of the component management server device 30. The parts management server device 30 is a so-called general-purpose computer, and includes a CPU 30a, a RAM 30b, a communication adapter 30c, and a storage device 30d. The CPU 30a, the RAM 30b, and the communication adapter 30c exhibit the same functions as those of the personal computers 13 and 23 described above.

  The storage device 30d is an auxiliary storage device built in the component management server device 30, and stores various programs that are read and executed on the RAM 30b by the CPU 30a and tables used when executing the various programs. Yes.

  Specifically, in addition to the OS program, the component information management table 31, the inventory component management table 32, the component state management table 33, the vehicle information management table 34, and the information transmission program 35 are installed in the storage device 30d. ing.

  The component information management table 31 is a table for managing information related to all components handled by a supplier who uses this component management system. FIG. 7 is a diagram illustrating an example of the data structure of the component information management table 31. The record in the component information management table 31 of FIG. 7 has fields of “component ID” and “component name”.

  Here, the “component ID” is a field in which the component IDs of all the components handled by the supplier are recorded. “Part name” is a field in which the name of the part is recorded.

  The inventory parts management table 32 is a table for managing information related to parts stored in the parts warehouse and the maintenance shop by the above-mentioned company as inventory parts. FIG. 8 is a diagram illustrating an example of the data structure of the inventory parts management table 32. The records in the inventory parts management table 32 in FIG. 8 have fields of “part ID”, “part warehouse inventory quantity”, and “maintenance factory inventory quantity”.

  Here, the “part ID” is a field in which part IDs of all parts stored in the parts warehouse and the maintenance factory by the above-mentioned dealer as stock parts are recorded. The “number of parts warehouse inventory” is a field in which the number of parts stored as inventory parts in the parts warehouse is recorded. The “maintenance factory inventory quantity” is a field in which the number of parts stored as inventory parts in the maintenance shop is recorded.

  The component state management table 33 is a table for managing information related to components that have been sold, repaired, and returned. FIG. 9 is a diagram illustrating an example of the data structure of the component state management table 33. The record in the component status management table 33 in FIG. 9 has fields of “component ID”, “number”, “status”, and “occurrence date”.

  Here, the “part ID” is a field in which the part ID of a part sold, repaired and returned is recorded. “Number” is a field in which the number of parts sold, repaired and returned is recorded. The “state” is a field in which part state information indicating whether the part has been sold, repaired, or returned is recorded. The “occurrence date and time” is a field in which the date and time when the part is sold, repaired and returned is recorded as the occurrence date and time information.

  The vehicle information management table 34 is a table for managing information related to vehicles that are allowed to enter the parts warehouse and maintenance shop of the above-mentioned supplier. FIG. 10 is a diagram showing an example of the data structure of the vehicle information management table 34. The record in the vehicle information management table 34 of FIG. 10 has fields of “vehicle ID” and “vehicle type”.

  Here, the “vehicle ID” is a field in which a vehicle ID, which is identification information uniquely assigned to each vehicle in order to individually identify the vehicle, is recorded. The “vehicle type” is a field in which vehicle type information indicating the owner of a vehicle permitted to enter the parts warehouse and maintenance shop of the above-mentioned supplier is recorded. In addition, when the vehicle is a vehicle owned by the supplier, the vehicle type information includes its use.

  The information transmission program 35 is a program for transmitting data to the database device 40 of another system used by the above-mentioned contractor. The contents of processing executed by the CPU 30a according to the information transmission program 35 will be described later.

  There are various database devices 40 of other systems to which the CPU 30a transmits data in accordance with the information transmission program 35. In the present embodiment, a sales management database device is used as an example. FIG. 11 is a diagram illustrating an example of a data structure of the sales management database table 41 stored in the sales management database device 40. The records in the sales management database table 41 of FIG. 11 have fields of “part ID”, “number”, “state”, and “occurrence date”. The information recorded in these fields is the same information as the information recorded in each field of each record in the component state management table 33 described above.

  The contents of processing executed in the component management system configured as described above will be described below.

  In the parts warehouse gate device 10, when the main power is turned on, the CPU 13a reads the electronic tag monitoring program 16 from the HDD 13i and starts the electronic tag monitoring process. FIG. 12 is a flowchart showing the contents of the electronic tag monitoring process.

  In the first step S101 after the start of the electronic tag monitoring process, the CPU 13a waits until data is received from the electronic tag via the electronic tag reader 13f (S101; NO). When data is received from the electronic tag through the electronic tag reader 13f (S101; YES), the CPU 13a advances the process to step S102.

  In step S102, the CPU 13a counts the number of component IDs in the data received in step S101. Subsequently, the CPU 13a includes a record including the component ID, the number, passing gate information indicating the gate antenna that has received the data, and passing date information indicating the date and time when the data is received, in the passing component journal table 14 in the HDD 13i. Record additional.

  In the next step S103, when the vehicle ID is included in the data received in step S101, the CPU 13a displays the vehicle ID, passing gate information indicating the gate antenna that received the data, and the date and time when the data was received. A record including the passing date and time information shown is additionally recorded in the passing vehicle journal table 15 in the HDD 13i.

  In the next step S104, the CPU 13a stands by until data is received from the electronic tag via the electronic tag reader 13f (S104; NO). When data is received from the electronic tag through the electronic tag reader 13f (S104; YES), the CPU 13a advances the process to step S105.

In step S105, CPU 13a counts the number of component ID in the received data in step S10 4. Subsequently, the CPU 13a includes a record including the component ID, the number, passing gate information indicating the gate antenna that has received the data, and passing date information indicating the date and time when the data is received, in the passing component journal table 14 in the HDD 13i. Record additional.

In the next step S106, CPU 13a, when it contains the vehicle ID in the data received in step S10 4, receives its vehicle ID, a pass gate information indicating a gate antenna that has received the data, the data time Is additionally recorded in the passing vehicle journal table 15 in the HDD 13i.

  In the next step S107, the CPU 13a additionally records the values in the “pass gate” field of the records additionally recorded in the journal tables 14 and 15 in steps S102 and S103, and additionally records in the journal tables 14 and 15 in steps S105 and S106. Based on the value of the “pass gate” field of the record, it is determined whether or not the electronic tag whose data has been received in steps S101 and S104 has been carried into the parts warehouse. If it is determined that the electronic tag has been carried into the parts warehouse (S107; YES), the CPU 13a advances the process to step S108.

  In step S108, the CPU 13a activates the parts warehouse program 17 in the HDD 13i.

  In the next step S109, the CPU 13a delivers information indicating the delivery to the parts warehouse program 17 started in step S108. This information includes the component ID, the number, and the vehicle ID if the vehicle ID is included in the data received in step S101, and the passage date and time additionally recorded in the passage component journal table 14 in step S102. Information. Thereafter, the CPU 13a ends the electronic tag monitoring process.

On the other hand, in step S107, CPU 13a, when the electronic tag data has been received in step S101 and S104 is determined to have been issued transportable from parts warehouse (S107; NO), the process proceeds to step S110.

  In step S110, the CPU 13a activates the parts warehouse program 17 in the HDD 13i.

  In the next step S111, the CPU 13a delivers information indicating the carry-out to the parts warehouse program 17 started in step S110. This information includes the component ID, the number, and the vehicle ID if the vehicle ID is included in the data received in step S101, and the passage date and time additionally recorded in the passage component journal table 14 in step S102. Information. Thereafter, the CPU 13a ends the electronic tag monitoring process.

  The CPU 13a that executes steps S101 to S106 and the electronic tag reader 13f correspond to the tag information reader described above.

  When the above-described electronic tag monitoring process ends, the CPU 13a of the parts warehouse gate device 10 immediately reads the electronic tag monitoring program 16 and starts the electronic tag monitoring process again. Therefore, the parts warehouse gate apparatus 10 always monitors the passage of the electronic tags of the gate antennas 11 and 12.

  Then, in the parts warehouse gate apparatus 10, when the parts warehouse program 17 is activated in the above-described electronic tag monitoring process, the parts warehouse process is started. 13 and 14 are flowcharts showing the contents of the parts warehouse processing.

  In the first step S201 after the start of the parts warehouse process, the CPU 13a determines whether or not the information received from the electronic tag monitoring process indicates the carry-in. If the CPU 13a determines that the information received from the electronic tag monitoring process indicates delivery (S201; YES), the CPU 13a advances the process to step S202.

  The CPU 13a that executes Step 201 and Steps S107 to S111 corresponds to the aforementioned entry / exit determination means.

  In step S202, the CPU 13a determines whether or not the vehicle ID is included in the information received from the electronic tag monitoring process. If the CPU 13a determines that the vehicle ID is not included in the information received from the electronic tag monitoring process (S202; NO), the process proceeds to step S204, and the vehicle ID is included in the information received from the electronic tag monitoring process. If it is determined that it is included (S202; YES), the process proceeds to step S203.

  In step S203, the CPU 13a refers to the vehicle information management table 34 in the parts management server device 30 to determine whether or not the vehicle ID indicates a parts supplier's vehicle. If it is determined that the vehicle ID indicates a vehicle of a parts supplier (S203; YES), the CPU 13a advances the process to step S204.

  In step S204, the CPU 13a identifies a record in which the component ID included in the information received from the electronic tag monitoring process in the inventory component management table 32 in the component management server device 30 is recorded in the “component ID” field. The number included in the information received from the electronic tag monitoring process is added to the value in the “number of parts warehouse inventory” field. After the addition, the CPU 13a ends the parts warehouse process.

  On the other hand, when the CPU 13a determines in step S203 that the vehicle ID does not indicate a vehicle of a parts supplier (S203; NO), the CPU 13a determines that the vehicle is its own vehicle or a forklift and advances the process to step S205. .

  In step S205, the CPU 13a specifies a record in which the component ID included in the information received from the electronic tag monitoring process in the inventory component management table 32 in the component management server apparatus 30 is recorded in the “component ID” field. The number included in the information received from the electronic tag monitoring process is added to the value in the “number of parts warehouse inventory” field. After the addition, the CPU 13a advances the process to step S206.

  The CPU 13a that executes steps S204 and S205 corresponds to the counting unit described above.

  In step S206, the CPU 13a records a new record in the component state management table 33 in the component management server device 30. In this new record, “parts warehouse return” is recorded in the “status” field, and in the “occurrence date and time” field, the same date and time as the passage date and time information included in the information received from the electronic tag monitoring process In the remaining fields, the component ID and the number included in the information received from the electronic tag monitoring process are recorded. After adding such a new record to the component state management table 33, the CPU 13a ends the component warehouse processing.

  In step S201, if the CPU 13a determines that the information received from the electronic tag monitoring process indicates carrying out (S201; NO), the process proceeds to step S207.

  In step S207, the CPU 13a determines whether or not the vehicle ID is included in the information received from the electronic tag monitoring process. If the CPU 13a determines that the vehicle ID is not included in the information received from the electronic tag monitoring process (S207; NO), the part is not carried out at the same time as the vehicle. Therefore, the process proceeds to step S211, and if it is determined that the vehicle ID is included in the information received from the electronic tag monitoring process (S207; YES), the process proceeds to step S208.

  In step S208, the CPU 13a refers to the vehicle information management table 34 in the component management server device 30 to determine whether or not the vehicle ID indicates a vehicle of a component supplier. When it is determined that the vehicle ID indicates a vehicle of a parts supplier (S208; YES), the CPU 13a advances the process to step S209.

  In step S209, the CPU 13a identifies a record in which the component ID included in the information received from the electronic tag monitoring process in the inventory component management table 32 in the component management server device 30 is recorded in the “component ID” field. The value in the “number of parts warehouse inventory” field is subtracted by the number included in the information received from the electronic tag monitoring process. After the subtraction, the CPU 13a ends the parts warehouse process.

  On the other hand, if the CPU 13a determines in step S208 that the vehicle ID does not indicate the vehicle of the parts supplier (S203; NO), the process proceeds to step S210.

  In step S210, the CPU 13a refers to the vehicle information management table 34 in the component management server device 30 to determine whether or not the vehicle ID indicates the vehicle of the company. If the CPU 13a determines that the vehicle ID indicates the company's vehicle (S210; YES), the CPU 13a advances the process to step S211.

  In step S211, the CPU 13a identifies a record in which the component ID included in the information received from the electronic tag monitoring process in the inventory component management table 32 in the component management server apparatus 30 is recorded in the “component ID” field. The value in the “number of parts warehouse inventory” field is subtracted by the number included in the information received from the electronic tag monitoring process.

  In the next step S212, the CPU 13a records a new record in the component state management table 33 in the component management server device 30. “Parts sales” is recorded in the “status” field of this new record, and the same date and time as the passage date information included in the information received from the electronic tag monitoring process is displayed in the “occurrence date” field. In the remaining fields, the component ID and the number included in the information received from the electronic tag monitoring process are recorded. After adding such a new record to the component state management table 33, the CPU 13a ends the component warehouse processing.

  On the other hand, if the CPU 13a determines in step S210 that the vehicle ID does not indicate its own vehicle (S210; YES), the CPU 13a determines that the vehicle ID indicates a forklift and advances the process to step S213.

  In step S213, the CPU 13a specifies a record in which the component ID included in the information received from the electronic tag monitoring process in the inventory component management table 32 in the component management server device 30 is recorded in the “component ID” field. The value in the “number of parts warehouse inventory” field is subtracted by the number included in the information received from the electronic tag monitoring process. After the subtraction, the CPU 13a advances the process to step S214.

  The CPU 13a that executes steps S209, S211, and S213 corresponds to the counting unit described above.

  In step S <b> 214, the CPU 13 a records a new record in the component state management table 33 in the component management server device 30. In this new record, “provisional sales” is recorded in the “status” field, and in the “occurrence date” field, the same year, month, day, hour, minute, and second as the passage date information included in the information received from the electronic tag monitoring process In the remaining fields, the component ID and the number included in the information received from the electronic tag monitoring process are recorded. After adding such a new record to the component state management table 33, the CPU 13a ends the component warehouse processing.

  Since such a part warehouse process is executed, the parts warehouse gate apparatus 10 has the parts attached with the electronic tag loaded on the parts supplier's vehicle and dives the gate antennas 11 and 12 into the parts warehouse. When the parts are brought in, it is reflected in the inventory parts management table 32 that the parts are purchased from a parts supplier (S201; YES, S202; YES, S203; YES, S204), and an electronic tag is pasted. When the parts are loaded on their own vehicles or forklifts and are carried into the parts warehouse through the gate antennas 11 and 12, it is confirmed that the parts are returned from the customer or the maintenance shop. Reflected in the table 32 and the component state management table 33 (S201; YES, S202; YES, S203; NO, S205, 206).

  The parts warehouse gate device 10 is also configured such that when a part to which an electronic tag is attached is loaded on a parts supplier's vehicle and is carried out of the parts warehouse through the gate antennas 11 and 12, the part is sent to the parts supplier. The returned parts are reflected in the inventory parts management table 32 (S201; NO, S207; YES, S208; YES, S209), and the parts to which the electronic tag is attached are loaded on the company's vehicle. When the gate antennas 11 and 12 are diverted from the parts warehouse, the fact that the parts are sold to the customer is reflected in the inventory part management table 32 and the part state management table 33 (S201; NO, S207; YES, S208; NO, S210; YES, S211, S212), the component with the electronic tag attached is a fork riff The inventory parts management table 32 and the parts state management table indicate that the parts are delivered to the maintenance shop and temporarily sold when the parts are loaded onto the gate antenna 11 and 12 and are carried out of the parts warehouse. 33 (S201; NO, S207; YES, S208; NO, S210; NO, S213, S214).

  In the maintenance shop gate device 20, when the main power is turned on, the CPU 23a reads the electronic tag monitoring program 26 from the HDD 23i, and starts the electronic tag monitoring process. Since the contents of the electronic tag monitoring process have been described above with reference to FIG. 12, detailed description of the contents of the electronic tag monitoring process is omitted.

  In the electronic tag monitoring process executed in the maintenance shop gate device 20, the tables in which records are recorded in steps S102, S103, S105, and S106 are the passing part journal table 24 and the passing vehicle journal of the maintenance shop gate device 20. Table 25. The program activated in steps S108 and S110 is a maintenance shop program 27.

  Further, when the electronic tag monitoring process ends, the CPU 23a of the maintenance shop gate device 20 immediately reads the electronic tag monitoring program 26 and starts the electronic tag monitoring process again. Therefore, the maintenance shop gate device 20 constantly monitors the passage of the electronic tags of the gate antennas 21 and 22.

  By the way, in this embodiment, the usage form of loading parts on the vehicle and passing through the gate antennas 21 and 22 is not adopted, and the parts are always loaded on the vehicle and the gate antennas 21 and 22 are loaded. Pass through. Therefore, the vehicle ID is always included in the information delivered to the maintenance shop program 27 in the electronic tag monitoring process.

  In the maintenance shop gate device 20, when the maintenance shop program 27 is activated in the above-described electronic tag monitoring process, the maintenance shop process is started. 15 and 16 are flowcharts showing the contents of the processing for the maintenance shop.

  In the first step S301 after the start of the maintenance shop process, the CPU 23a determines whether or not the information received from the electronic tag monitoring process indicates the carry-in. If it is determined that the information received from the electronic tag monitoring process indicates the carry-in (S301; YES), the CPU 23a advances the process to step S302.

  The CPU 23a that executes Step S301 and Steps S107 to S111 of the electronic tag monitoring process of FIG. 12 corresponds to the aforementioned entry / exit discrimination means.

  In step S302, the CPU 23a refers to the vehicle information management table 34 in the component management server device 30, so that the vehicle ID included in the information received from the electronic tag monitoring process indicates the customer's vehicle. It is determined whether or not. If the CPU 23a determines that the vehicle ID indicates the customer's vehicle (S302; YES), the CPU 23a ends the maintenance shop process, and determines that the vehicle ID does not indicate the customer's vehicle (S302). NO), the process proceeds to step S303.

  In step S303, the CPU 23a refers to the vehicle information management table 34 in the parts management server device 30, so that the vehicle ID included in the information received from the electronic tag monitoring process indicates the vehicle of the company. It is determined whether or not. If the CPU 23a determines that the vehicle ID does not indicate its own vehicle (S303; NO), the CPU 23a proceeds to step S309 and determines that the vehicle ID indicates its own vehicle (S303; YES). ), The process proceeds to step S304.

  In step S304, the CPU 23a identifies the record when the vehicle with the vehicle ID last passed through the gate antennas 21 and 22 among the records in the passing vehicle journal table 25 in the HDD 23i. Read the passage date information in the “Date” field. Subsequently, the CPU 23a identifies a record in which the read passage date / time information is specified in the “passing date / time” field among the records in the passage component journal table 24 in the HDD 23i, and the “number” of the identified records. The number recorded in the field is read as the number at the time of carry-out.

  In the next step S305, the CPU 23a determines whether or not the number of carry-in included in the information received from the electronic tag monitoring process is smaller than the number of carry-out read in step S304. . If the CPU 23a determines that the number at the time of carry-in is the same as the number at the time of carry-out (S305; NO), the CPU 23a advances the process to step S308, and the number at the time of carry-in is smaller than the number at the time of carry-out. (S305; YES), the process proceeds to step S306.

  In step S306, the CPU 23a calculates the number of parts sold in the business trip repair by subtracting the number at the time of carry-in from the number at the time of carry-out.

  In the next step S307, the CPU 23a records a new record in the component state management table 33 in the component management server device 30. In this new record, the “status” field records “business trip repair sales”, and the “occurrence date” field contains the same year, month, day, hour, minute, second as the passage date information included in the information received from the electronic tag monitoring process. In the “component ID” field, the component ID included in the information received from the electronic tag monitoring process is recorded, and in the “number” field, the number calculated in step S306 is recorded. After adding such a new record to the component state management table 33, the CPU 23a advances the process to step S308.

  In step S <b> 308, the CPU 23 a records a new record in the component state management table 33 in the component management server device 30. In this new record, the “status” field records “business trip repair / return”, and the “occurrence date / time” field indicates the same date / time / hour / minute / second as the passing date / time information included in the information received from the electronic tag monitoring process. In the remaining fields, the component ID and the number included in the information received from the electronic tag monitoring process are recorded. After adding such a new record to the component state management table 33, the CPU 23a advances the process to step S309.

  In step S309, the CPU 23a specifies a record in which the component ID included in the information received from the electronic tag monitoring process in the inventory component management table 32 in the component management server apparatus 30 is recorded in the “component ID” field. The value in the “maintenance factory inventory” field is subtracted by the number included in the information received from the electronic tag monitoring process. After the subtraction, the CPU 23a ends the process for the maintenance shop.

  The CPU 23a executing step S309 corresponds to the counting unit described above.

  On the other hand, in step S301, when the CPU 23a determines that the information received from the electronic tag monitoring process indicates carrying out (S301; NO), the process proceeds to step S310.

  In step S310, the CPU 23a refers to the vehicle information management table 34 in the component management server device 30, so that the vehicle ID included in the information received from the electronic tag monitoring process indicates the vehicle of the company. It is determined whether or not. If it is determined that the vehicle ID indicates the vehicle of the company (S310; YES), the CPU 23a advances the process to step S311.

  In step S <b> 311, the CPU 23 a records a new record in the component state management table 33 in the component management server device 30. In this new record, the “status” field records “business trip repair sales”, and the “occurrence date” field contains the same year, month, day, hour, minute, second as the passage date information included in the information received from the electronic tag monitoring process. In the remaining fields, the component ID and the number included in the information received from the electronic tag monitoring process are recorded. After adding such a new record to the component state management table 33, the CPU 23a advances the process to step S321.

  On the other hand, if the CPU 23a determines in step S310 that the vehicle ID does not indicate the customer's vehicle (S310; NO), the process proceeds to step S312.

  In step S312, the CPU 23a refers to the vehicle information management table 34 in the parts management server device 30, so that the vehicle ID included in the information received from the electronic tag monitoring process indicates the customer's vehicle. It is determined whether or not. When the CPU 23a determines that the vehicle ID does not indicate the customer's vehicle (S312; NO), the CPU 23a proceeds to step S321, and determines that the vehicle ID indicates the customer's vehicle (S312; YES), the process proceeds to step S313.

  In step S313, the CPU 23a identifies the record when the vehicle with the vehicle ID last passed through the gate antennas 21 and 22 among the records in the passing vehicle journal table 25 in the HDD 23i. Read the passage date information in the “Date” field. Subsequently, the CPU 23a identifies a record in which the read passage date / time information is specified in the “passing date / time” field among the records in the passage component journal table 24 in the HDD 23i, and the “number” of the identified records. The number recorded in the field is read as the number at the time of admission.

  In the next step S314, the CPU 23a determines whether or not the number of times of entry included in the information received from the electronic tag monitoring process is smaller than the number of times of entry read in step S313. . If it is determined that the number at the time of entry is smaller than the number at the time of entry (S314; YES), the CPU 23a advances the process to step S315.

  In step S315, the CPU 23a calculates the number of parts returned in the carry-in repair by subtracting the number at the time of entry from the number at the time of entry.

  In the next step S316, the CPU 23a records a new record in the component state management table 33 in the component management server device 30. In this new record, the “status” field records “business trip repair / return”, and the “occurrence date / time” field indicates the same date / time / hour / minute / second as the passing date / time information included in the information received from the electronic tag monitoring process. In the remaining fields, the component ID and the number included in the information received from the electronic tag monitoring process are recorded. After adding such a new record to the component state management table 33, the CPU 23a advances the process to step S317.

  In step S317, the CPU 23a specifies a record in which the component ID included in the information received from the electronic tag monitoring process in the inventory component management table 32 in the component management server device 30 is recorded in the “component ID” field. The number included in the information received from the electronic tag monitoring process is added to the value in the “maintenance factory inventory” field. After adding, CPU23a complete | finishes the process for maintenance shops.

  The CPU 23a executing step S317 corresponds to the counting unit described above.

  On the other hand, if the CPU 23a determines in step S314 that the number at the time of entry is not less than the number at the time of entry (S314; NO), the process proceeds to step S318.

  In step S318, the CPU 23a determines whether or not the number of entries included in the information received from the electronic tag monitoring process is greater than the number of entries read in step S313. If it is determined that the number at the time of entry is larger than the number at the time of entry (S318; YES), the CPU 23a advances the process to step S319.

  In step S319, the CPU 23a calculates the number of parts sold in the carry-in repair by subtracting the number at entry from the number at entry.

  In the next step S320, the CPU 23a records a new record in the component state management table 33 in the component management server device 30. In this new record, the “status” field records “business trip repair sales”, and the “occurrence date” field contains the same year, month, day, hour, minute, second as the passage date information included in the information received from the electronic tag monitoring process. In the remaining fields, the component ID and the number included in the information received from the electronic tag monitoring process are recorded. After adding such a new record to the component state management table 33, the CPU 23a advances the process to step S321.

  In step S321, the CPU 23a specifies a record in which the component ID included in the information received from the electronic tag monitoring process in the inventory component management table 32 in the component management server apparatus 30 is recorded in the “component ID” field. The value in the “maintenance factory inventory” field is subtracted by the number included in the information received from the electronic tag monitoring process. After the subtraction, the CPU 23a ends the process for the maintenance shop.

  The CPU 23a executing step S321 corresponds to the counting unit described above.

  On the other hand, in step S318, if the CPU 23a determines that the number at the time of entry is not larger than the number at the time of entry (S318; NO), the number of times at the time of entry and the number at the time of entry are determined to be the same. Then, the processing for the maintenance shop is completed.

  Since such a process for the maintenance shop is executed, the maintenance shop gate apparatus 20 loads the parts with the electronic tag attached thereto on the customer's vehicle and enters the maintenance shop through the gate antennas 21 and 22. When this is done, no information is reflected in the inventory part management table 32 and the part state management table 33 (S301; YES, S302; YES), and the part with the electronic tag attached is loaded on the vehicle of its own. If the gate antennas 21 and 22 are diverted into the maintenance factory and the number is less than the number at the time of carry-out, the reduced parts are sold during business trip repair. Reflected in the component management table 32 and the component state management table 33 (S301; YES, S302; NO, S303; YES, S305; YES, S306) S309) If the number is the same as the number at the time of carry-out, it is reflected in the inventory parts management table 32 and the parts state management table 33 that the items temporarily sold in the business trip repair are returned (S301; YES, S302). NO, S303; YES, S305; NO, S308, S309).

  In addition, when the parts to which the electronic tag is attached are loaded on the company's vehicle and are carried out of the maintenance factory through the gate antennas 21 and 22, the maintenance shop gate device 20 repairs the parts on a business trip to the customer. Is reflected in the inventory part management table 32 and the part state management table 33 (S301; NO, S310; YES, S311, S321), and the part to which the electronic tag is attached is transferred to the forklift. When loaded and dived from the maintenance shop through the gate antennas 21 and 22, the stock parts management table 32 reflects that the parts are delivered to the parts warehouse and returned (S301; NO) , S310; NO, S312; NO, S321), the part with the electronic tag attached is loaded on the customer's vehicle. When the antennas 21 and 22 are diverted from the maintenance factory and the number of parts is less than the number at the time of delivery, the reduced parts are returned to the maintenance factory from the customer. If it is reflected in the parts management table 32 and the parts state management table 33 (S301; NO, S312; YES, S313, S314; YES, S315 to S317) Is sold in maintenance at a maintenance shop is reflected in the inventory part management table 32 and the part state management table 33 (S301; NO, S312; YES, S313, S314; NO, S318; YES, S319) ~ S321).

  In parallel with the parts warehouse process and the maintenance shop process described above, the parts management server device 30 selects any one of parts sales, carry-in repair sales, and business trip repair sales for the part status management table 33. When a record recorded in the “status” field is added, using this as a trigger, the CPU 30a reads the information transmission program 35 from the HDD 30d and starts information transmission processing.

  In this information transmission process, the CPU 30 a transmits the record added to the component state management table 33 to the sales management database device 40. When the sales management database device 40 receives this record, it additionally records it in the sales management database table 41.

  As described above, according to the parts management system of the present embodiment, the number of parts loaded on a vehicle and carried out from a facility such as a parts warehouse or a maintenance factory is counted as the number of sales and is loaded on the vehicle. The number of parts brought into the facility is counted as the number of returns. Accordingly, the sales management database device 40 can easily calculate the sales of the part by multiplying the number obtained by subtracting the number of returned goods from the number of sales by the price of the part. That is, it becomes possible to manage the sales of parts in the facility.

Schematic diagram of a parts management system according to an embodiment of the present invention Configuration diagram of personal computer for parts warehouse gate system The figure which shows an example of the data structure of a passage parts journal table The figure which shows an example of the data structure of a passing vehicle journal table Configuration diagram of the personal computer of the gate of the maintenance shop Configuration diagram of the parts management server device The figure which shows an example of the data structure of a components information management table The figure which shows an example of the data structure of an inventory components management table The figure which shows an example of the data structure of a component state management table The figure which shows an example of the data structure of a vehicle information management table The figure which shows an example of the data structure of a sales management database table Flow chart showing contents of electronic tag monitoring process Flow chart showing contents of parts warehouse processing Flow chart showing contents of parts warehouse processing Flowchart showing details of processing for maintenance shop Flowchart showing details of processing for maintenance shop

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 Parts warehouse gate apparatus 11 Gate antenna 12 Gate antenna 13 Personal computer 13a CPU
13b RAM
13e Communication adapter 13f Electronic tag reader 13i HDD
14 Passing parts journal table 15 Passing vehicle journal table 16 Electronic tag monitoring program 17 Parts warehouse program 20 Maintenance shop gate device 21 Gate antenna 22 Gate antenna 23 Personal computer 23a CPU
23b RAM
23e communication adapter 23f electronic tag reader 23i HDD
24 Passing Parts Journal Table 25 Passing Vehicle Journal Table 26 Electronic Tag Monitoring Program 27 Maintenance Shop Program 30 Parts Management Server Device 30a CPU
30b RAM
30c Communication adapter 30d Storage device 31 Parts information management table 32 Inventory parts management table 33 Parts status management table 34 Vehicle information management table 35 Information transmission program 40 Sales management database device 41 Sales management database table N network

Claims (3)

Computer
It is a vehicle from the electronic tag attached to the vehicle while reading the component information indicating that it is a component from the electronic tag attached to the component via the electronic tag reader installed at the entrance and exit of the facility. Tag information reading means for reading vehicle information including information indicating the vehicle user and
Based on the part information read by the tag information reading means and the vehicle information, an entry / exit judgment means for judging whether the part has been carried out by the vehicle, or
When the entry / exit determination means determines that the part has been carried out, and the vehicle information is information indicating a customer's vehicle, the number of parts is recorded as a sales number in the storage device, and the entry / exit determination means If the vehicle information is information indicating a customer's vehicle, the number of the parts is recorded as the number of returned items in the storage device. Parts management program. The component information includes information indicating the type of component,
2. The parts management program according to claim 1, wherein the counting means counts the number of sales or the number of returned goods recorded in the storage device for each type of part. In the case where the counting means determines that the part has been carried out, and the vehicle information is information indicating a customer's vehicle, the number of the parts is carried in simultaneously with the customer's vehicle. It is determined whether it is decreasing or increasing from the number of times, and if it is decreasing, the number obtained by subtracting the number of parts from the number at the time of carry-in is recorded in the storage device as the number of returned parts of the parts and, if the increase, the number obtained by subtracting the number of time carrying the number of the components, according to claim 1, wherein the component management program and recording in the storage device as sales of the components .

Images