JP2010009503A - Article management system, local side control device, information processing method, and program for local side control device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an article management system facilitating development, maintenance and operation of a system. <P>SOLUTION: The article management system (1) acquires information in a radio electronic tag provided in an article to be carried out from a place and manages the article. The article management system 1 includes a SaaS management device (3) for consolidating information showing that the article is carried out and returned in each place, and a local side control device (2c) installed in each place in a communicable manner with the SaaS management device through a communication network to generate information about whether the article is carried out or returned on the basis of acquisition information acquired from the radio electronic tag and temporarily stores the generated information. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a take-out management system, a local-side control device, an information processing method, and a program for a local-side control device, and more particularly, a field RFID control process using SaaS in a take-out management system composed of SaaS and UHF band RFID gates. Related to things that automatically work with.

  Management of take-out information is carried out at each distribution base and each factory. In recent years, the use of the system has been studied due to the progress of RFID (Rdio Frequency IDentification) technology, but the systemization will be in full swing in the future.

  As a technology related to the take-out information management system, for example, Patent Document 1 shown below can be cited.

Patent Document 1 discloses an asset take-out management system. In this asset take-out management system, an electronic tag that stores a unique ID for each electronic tag is affixed to an asset such as a personal computer, and the take-out person of the asset such as a personal computer operates the asset take-out application device, Apply for permission to take out assets such as personal computers to the email address.
The superior of the person taking out assets such as a personal computer operates the asset take-out permission device and permits the taking out of assets such as a personal computer.
The asset take-out permission device transmits information indicating assets such as a personal computer permitted to be taken out to a take-out check management device installed near the doorway.
The take-out check management apparatus determines whether or not the take-out check management apparatus is a normal take-out based on the received information indicating the assets such as a personal computer permitted to be taken out and the information stored in the electronic tag.

  Also, in Patent Document 1, the asset take-out management system stores information including a unique ID for each electronic tag and transmits an electronic tag (wireless information storage means) that transmits information stored by wireless communication. ), The ID stored in the electronic tag, the asset management number of the asset such as the personal computer with the electronic tag attached, the information identifying the user, the information on the place of use, and the asset such as the personal computer are taken out It includes an asset database management device (asset database management means) that manages an asset database that stores information indicating whether it is in-house or in-house asset status.

  Furthermore, the asset take-out management system disclosed in Patent Document 1 is an asset take-out application device (asset take-out application means), in which an asset take-out person such as a personal computer applies to a supervisor for permission to take out assets such as a personal computer. An asset take-out permitting device (assets take-out permitting means) that allows a boss to take out assets such as personal computers, and a metal sensing device that is installed near the entrance and that detects metal objects ( Metal object detection means), ID stored in the electronic tag is read, and a check-out management device (take-out check management) that identifies whether an asset such as a personal computer to which the electronic tag is attached is allowed to be taken out Means), and an in-house communication network (communication network) connecting the asset database, the asset take-out application device, the asset take-out permission device, and the take-out check management device 105 Including.

The asset database management device includes an electronic tag reader / writer and a computer such as a personal computer equipped with database management software for managing the asset database.
When an asset database management device administrator introduces an asset such as a personal computer, the electronic tag is attached to the asset such as a personal computer, and the electronic tag reader / writer reads the ID stored in the attached electronic tag to manage the asset database. Check that the asset management number, product name, information for identifying the user, information on the location of use, and the assets such as the personal computer are in an in-house asset state by operating a computer such as a personal computer equipped with the database management software. The information to be shown is input and stored in the asset database in association with the ID stored in the electronic tag.
JP 2005-284505 A

  By the way, in the asset take-out management system of Patent Document 1, it is necessary to install an asset database management device for each site such as a usage site, and the system cannot be easily deployed, maintained, and operated. there were.

  In addition, when the SaaS service is stopped due to periodic maintenance or failure, there is a problem that the system operation at the use site cannot be continued without stopping.

  An object of the present invention is to solve the above-described problems of the related art, and a take-out management system, a local side control device, an information processing method, and a local side that can easily perform system development, maintenance, and operation. It is to provide a control device program.

  In order to achieve the above object, a take-out management system of the present invention is a take-out management system that acquires information in a wireless electronic tag provided in an article taken out from a use site and manages the article, and each use site The SaaS management device that centrally manages the carry-out return information related to the take-out and return of the article, and the acquisition acquired from the wireless electronic tag that is installed at each use site so as to be able to communicate with the SaaS management device via a communication network A local-side control device that generates and temporarily holds take-out return information regarding take-out and return of the article based on the information.

  The local-side control device of the present invention is a local-side control that is installed at each use site so as to be communicable via a communication network with a SaaS management device that centrally manages take-out return information related to take-out and return of articles taken out from the use site. A local-side operation data holding unit that stores the take-out return information as log information, and a local-side transmission storage exchange unit that temporarily stores the take-out return information as queue information for transmitting to the SaaS management device. The take-out return information is generated as the log information and stored in the local-side operation data holding unit, and the take-out return information is generated as the queue information in the local-side transmission storage / exchange unit and the local-side operation data is held. And control means for controlling the local transmission storage exchange means It is characterized in that it comprises, when.

  The information processing method of the present invention is an information processing method in which a computer performs processing for acquiring information in a wireless electronic tag provided in an article taken out from a use site and managing the article, from the wireless electronic tag Based on the acquired information, take-out return information relating to take-out and return of the article is generated and stored as log information at the use site by the computer, and then the take-out return information by the computer at the use site. Is generated and temporarily stored as queue information for transmission to the SaaS management apparatus, and then the queue information is monitored by the computer and transmitted to the SaaS management apparatus via a communication network. It is a feature.

  The local control device program according to the present invention is a local control device installed at each use site so as to be able to communicate with a SaaS management device that centrally manages take-out return information regarding take-out and return of articles taken from the use site via a communication network. A program for a local control device capable of realizing various functions in a computer provided in the side control device, the first processing function for generating and storing the take-out return information as log information, and the take-out return A second processing function for generating and temporarily storing information as queue information for transmitting information to the SaaS management device, and a third processing for monitoring the queue information and transmitting the information to the SaaS management device via a communication network. And the processing function is realized by a computer.

  According to the present invention, the carry-out return information is centrally managed by the SaaS management device, and the local control device temporarily stores the information. Therefore, there is no need for a database management server at each distribution base and each factory, and each distribution base, Easy to deploy, maintain and operate in factories.

[Basic configuration of take-out management system]
First, the basic configuration of the take-out management system will be described. The take-out management system (for example, reference numeral 1 shown in FIG. 1) of the present invention acquires information in a wireless electronic tag (for example, reference numerals 42a, 42b, and 42c shown in FIG. 1) provided in an article taken out from the use site. The article is managed.

  This take-out management system includes a SaaS management device (for example, reference numeral 3 shown in FIG. 1) that centrally manages take-out return information regarding take-out and return of the article at each use site, and the SaaS management device and a communication network (for example, FIG. 1). Local side control which is installed at each use site so as to be communicable via N), and generates and temporarily holds take-out return information regarding take-out and return of the article based on acquisition information acquired from the wireless electronic tag An apparatus (for example, reference numeral 2c shown in FIG. 1).

  In addition, the local control device has a local operation data holding means for storing the take-out return information as log information (for example, reference numeral 14 shown in FIG. 1), and sends the take-out return information to the SaaS management device. Local transmission storage exchange means for temporarily storing as queue information (for example, reference numeral 20 shown in FIG. 1), the take-out return information is generated as the log information and stored in the local operation data holding means, and the local side The transmission accumulation exchange means includes control means (for example, reference numeral 12 shown in FIG. 1) that generates the take-out return information as the queue information and controls the local operation data holding means and the local transmission accumulation exchange means.

  In such a take-out management system, take-out return information is centrally managed by the SaaS management device, and the local control device temporarily stores the information. Therefore, there is no need for a database management server at each logistics base and factory, and each logistics base , Deployment to each factory, maintenance and operation become easy.

Also, the operation data can be held locally using the control means, and the delay of message exchange regarding take-out return information can be automatically synchronized. When the SaaS service is stopped due to regular maintenance or failure, system operation at the site of use can be performed. Can continue without stopping.
That is, by using the queue information and holding the log information on the local side, even when it is not possible to connect to the SaaS service, it is possible to perform check management when returning, etc. Service continuity can be secured.

  Hereinafter, an example of a preferred embodiment of such a “take-out management system” of the present invention will be specifically described with reference to the drawings.

[First Embodiment]
(Overall configuration of take-out management system)
First, the specific configuration of the take-out management system of the present embodiment will be described from the overall configuration, and then the detailed configuration of each unit will be described. FIG. 1 is a block diagram showing an example of an overall schematic configuration of the take-out management system according to the first embodiment of the present invention.

As shown in FIG. 1, the overall configuration of the take-out management system 1 according to the present embodiment is formed at a use site such that a management side system 3 such as a data center can be connected to the management side system 3 via a communication network N. And the local system 2 to be operated.
An example of the communication network N is the Internet. An example of the communication protocol is SOAP (Simple Object Access Protocol). In SOAP, messages (objects) can be exchanged between software.

  The management side system 3 considers application to a business AP (application), and includes a SaaS management system 62 having a SaaS management database for storing take-out management information, and SaaS that is a SaaS side cooperation interface function. Side transmission storage exchange function 64a, custom tab report acquisition / update function 66 for acquiring / updating information such as custom tab report, and master maintenance acquisition / update function for acquiring / updating information such as master maintenance 68.

  The local side system 2 transmits the UHF band RFID gate unit 30 as an acquisition device (acquisition means) for acquiring information from an RFID tag, which is an example of a wireless electronic tag, and the acquired acquisition information to the management side system 3. RFID control process 10 that is a local application that performs control, take-out return log information storage unit 16 that temporarily stores log information generated by RFID control process 10, and queue information generated by RFID control process 10 A local side transmission interface function 20 that temporarily stores information, a Web browser for using a custom tab report acquisition / update function 66 and a master maintenance acquisition / update function 68 in the management system 3 And an administrator terminal 50 equipped with .

The RFID control process 10 includes a local operation data holding function 14 that holds take-out management information locally, and a controller function 12 that controls the local operation data holding function 14 and the cooperation interface.
In this way, in the present embodiment, the SaaS management system 62 and the RFID control process 10 at the use site are used by using the controller function 12, the local operation data holding function 14, and the local side transmission storage and exchange function 20 which is a cooperation interface function. Can be linked automatically.

  The administrator terminal 50 is installed at the site of use and can acquire and update information of the SaaS management device.

Here, the hardware configuration of the management-side system 3 can be configured by, for example, a SaaS management device (computer) that operates by program control.
In the local system 2, the hardware configuration of the RFID control process 10, the take-out return log information storage unit 16, and the local transmission accumulation / exchange function 20 is, for example, the same as that of the local control device (computer) 2c that operates by program control. Can be configured.

  The computer as the SaaS management device constituting the management side system 3 operates by program control, and has a network-related communication function, and has a desktop, laptop computer, and other wireless / wired communication functions. Any computer such as an information device, an information home appliance (TV / portable music player / game machine), or a similar computer may be used, regardless of whether it is mobile or fixed.

  The hardware configuration of the computer as the SaaS management device constituting the management side system 3 includes a display unit (screen) for displaying various information and the like on the display screen of the display unit (various input fields, etc.) An operation input unit (such as a keyboard, mouse, various buttons, display operation unit <button on the screen>, touch panel, etc.), a transmission / reception unit or a communication unit (modem) for transmitting / receiving various signals / data Etc.), a storage unit (for example, a memory, a hard disk, etc.) for storing various programs and various data, and a control unit (for example, a CPU, MPU, DSP, etc.) for controlling these.

  The computer as the local control device 2c operates by program control, and if it has a network-related communication function, it can be a desktop, laptop computer, server computer, or other information device having a wireless / wired communication function. Any computer such as a computer similar to the above may be used, regardless of whether it is mobile or fixed.

The hardware configuration of the computer as the local control device 2c is for operating and inputting data on a display unit (screen) for displaying various information and the like on the display screen (various input fields, etc.) of the display unit. Operation input unit (for example, keyboard, mouse, various buttons, etc.), transmission / reception unit for transmitting / receiving various signals / data, or communication unit (modem, etc.), storage unit for storing various programs / various data (for example, memory, A hard disk, etc.), and a control unit (for example, CPU, MPU, etc.) for controlling these.
The administrator terminal 50 can be similarly configured by a computer.

The UHF band RFID gate unit 30 includes a first RFID tag 42c (first wireless electronic tag) attached to a user at a use site, for example, a mechanic, and second RFID tags 42a and 42b (first RFID tags attached to items taken out by the user). RFID antenna 34, which is a receiving antenna for receiving radio waves transmitted from (2 wireless electronic tags) or the like.
The RFID antenna 34 is installed at an entrance or the like through which a mechanic passes from the inside to the outside of the site of use. In FIG. 1, a total of four RFID antennas 34 are formed on each of the upper and lower stages. .

  In addition, the UHF band RFID gate unit 30 confirms that an RFID reader 32 as a reading device that reads information from the first RFID tag 42c and the second RFID tags 42a and 42b received by each RFID antenna 34, and that a mechanic has passed. Human sensors 36a and 36b are provided as detection means for detecting.

In the controller function 12 of the RFID control process 10, the local operation data holding function 14 is controlled, and the first acquisition information (mechanic ID and associated information) of the first RFID tag 42c (first wireless electronic tag) and the second RFID tag Generate log information (take-out log information / return log information) (for example, information shown in FIG. 16) by associating with the second acquired information (device ID and its associated related information) of 42a, 42b (second wireless electronic tag) Then, the generated log information is taken out and temporarily stored in the return log information storage unit 16.
Further, in the controller function 12 of the RFID control process 10, the first acquisition information (mechanic ID and its associated information) of the first RFID tag 42c (first wireless electronic tag) and the second RFID tags 42a, 42b (second wireless electronic Queue information (for example, information shown in FIG. 15) is generated by associating the second acquisition information (device ID and its associated information) of the tag), and the generated queue information is transmitted to the local-side transmission storage exchange function 20 (QUE ) Temporarily.

(Detailed configuration of the embodiment)
The detailed configuration of the present embodiment will be described with reference to FIG.
The SaaS management system 62 (SaaS management database server) shown in FIG. 1 has an access function from the SaaS side transmission storage and exchange function 64a, and has a function of storing take-out management information for business applications.

The SaaS transmission / reception exchange function 64a has a function of capturing a message from the local transmission / reception exchange function 20.
Further, the SaaS side transmission accumulation exchange function 64 a has an access function from the controller function 12.
Further, the SaaS side transmission storage and exchange function 64a has a function of taking a delay synchronization of message exchange for the business application.

The local side transmission accumulation and exchange function (QUE) 20 has an access function from the controller function 12.
In addition, the local side transmission accumulation and exchange function (QUE) 20 has a function of taking a delay synchronization of message exchange for the business application.

  The controller function 12 accesses the local operation data holding function 14 and controls the local operation data holding function 14, and accesses the local side transmission storage and exchange function (QUE) 20 to access the local side transmission storage and exchange function ( A second control function for controlling the QUE) 20 and a third control function for accessing the SaaS side transmission accumulation switching function 64a and controlling the SaaS side transmission accumulation switching function 64a.

  The local operation data holding function 14 can have a function of holding operation data on the local side for a business application.

Here, the configuration of the local transmission accumulation / exchange function (QUE) 20, the RFID control process 10, and the take-out return log information storage unit 16 of the present embodiment can also be referred to as an example of the “local control device 2 c”. The management-side system 3 of the present embodiment can also be referred to as an example of a “SaaS management device”.
Further, the local side transmission accumulation and exchange function (QUE) 20 of the present embodiment can be said to be an example of “local side transmission accumulation and exchange means”. Furthermore, the local operation data holding function 14 of the present embodiment can be said to be an example of “local operation data holding means”. Furthermore, the controller function 12 of the present embodiment can be said to be an example of “control means”.

The “local control device 2c” is installed at each use site so as to be able to communicate with the SaaS management device via a communication network, and is taken out for taking out and returning the article based on the acquired information acquired from the wireless electronic tag. Return information can be generated and stored temporarily.
The “local operation data holding unit” can store the take-out return information as log information.
The “local side transmission accumulation / exchange means” can temporarily accumulate the take-out return information as queue information for transmitting to the SaaS management apparatus.
The “control unit” generates the take-out return information as the log information, accumulates it in the local operation data holding unit, and generates and outputs the take-out return information as the queue information to the local-side transmission accumulation exchange unit The processing operation to be performed can be controlled.

  Further, the “control unit” monitors the queue information, and when the queue information of the local side transmission accumulation exchange unit is empty, transmits the queue information to the SaaS management device, and the queue information is When it is not empty, the queue information can be temporarily stored in the local-side transmission storage / exchange means, and then transmitted at regular intervals.

The wireless electronic tag may include a first wireless electronic tag attached to a user at the usage site and a second wireless electronic tag attached to the article taken out by the user.
In this case, the “control unit” can generate the log information by associating the first acquisition information of the first wireless electronic tag and the second acquisition information of the second wireless electronic tag.

  In addition, the “control unit” performs a collation determination based on the log information when the article is taken out when returning the article, and performs a process of deleting the log information when a match is determined. be able to.

(About operation)
The take-out management system configured as described above generally operates as follows.
First, as shown in FIG. 2, at the time of take-out, the RFID control process 10 acquires a read ID from the RFID manager 18, and the controller function 12 outputs take-out log information.

  Next, when the QUE in the local side transmission accumulation and exchange function (QUE) 20 is empty, the controller function 12 logs in to SaaS and outputs take-out information to the SaaS side transmission accumulation and exchange function 64a.

If the QUE is not empty, the controller function 12 calls a take-out API (Application Programming Interface).
When the take-out API is called, the controller function 12 outputs take-out information to the local-side transmission accumulation / exchange function 20.

The QUE in the local side transmission accumulation and exchange function (QUE) 20 automatically takes out information at regular intervals from the local side (local side transmission accumulation and exchange function 20) to the SaaS side (SaaS side transmission and accumulation exchange function 64a). .
Then, the take-out information is reflected in the SaaS management system (SaaS management database server) 62.

  At the time of return, the RFID control process 10 acquires the read ID from the RFID manager 18, and the controller function 12 compares the return information with the log information taken out and deletes it if they match.

Next, if the local QUE is empty, the controller function 12 logs in to SaaS and outputs the return information to the SaaS transmission and exchange function 64a.
If the QUE is not empty, the controller function 12 calls a return API.

When the return API is called, the controller function 12 outputs return information to the local side transmission accumulation exchange function 20.
The QUE automatically transfers return information from the local side to the SaaS side at regular intervals.
Then, the return information is reflected on the SaaS management system (SaaS management database server) 62.

(Configuration of custom objects)
FIG. 3 is an explanatory diagram illustrating an example of a configuration of a custom object on the (SaaS management database server) in the take-out management system according to the first embodiment.
The mechanic object 72 can include information such as a mechanic name, a mechanic ID (mechanic identifier), an employee number, a company name, and a department name.
The device object 74 can include, for example, information such as a device ID (device identifier), a device name, remarks, a last user, and a last use date.
The take-out / return status management object 76 can include information such as a management number, device ID, device name, take-out mechanic name, take-out date / time, return mechanic name, return date / time, and the like.

(Custom tab display screen configuration example 1)
FIG. 4 is an explanatory diagram showing an example of the configuration of a custom tab for expanding the custom object of FIG. 3 on the display screen.
In the first custom tab 100, an example of a display screen of the mechanic ID display unit 100a is disclosed.
The mechanic ID display unit 100a can display each piece of information related to the mechanic object 72, which is one of the custom objects shown in FIG.

The mechanic ID display unit 100a is a mechanic ID detail display unit 110 that displays details of mechanic ID incidental information related to the mechanic ID, and a take-out / return state that displays an item list of information related to take-out / return state management. The management information list display unit 120 is included.
The mechanic ID detail display unit 110 can display information such as a mechanic name, a mechanic ID (mechanic identifier), an employee number, a company name, a department name, a creator, and a last updater.
The take-out / return status management information list display unit 120 may display a list of actions such as device ID, device name, take-out date / time, return mechanic name, return date / time, and edit / delete for each management number. it can.

(Example 2 of custom tab display screen)
FIG. 5 is an explanatory diagram showing an example of a configuration of a custom tab for expanding the custom object of FIG. 3 on the display screen.
In the second custom tab 200, an example of the display screen of the take-out / return status management information display unit 200a is disclosed.
The take-out / return state management information display unit 200a can display each piece of information related to the take-out / return state management object 76, which is one of the custom objects shown in FIG.

The take-out / return state management information display unit 200a includes a take-out / return state management information list display unit 210 that displays a list of items related to take-out / return state management.
The take-out / return status management information list display unit 210 can display a list of device ID, device name, take-out date, return mechanic name, return date, etc. for each management number.

(Configuration example 3 of custom tab display screen)
FIG. 6 is an explanatory diagram showing an example of a configuration of a custom tab for expanding the custom object of FIG. 3 on the display screen.
In the third custom tab 300, an example of a display screen of the device ID display unit 300a is disclosed.
The device ID display unit 300a can display information related to the device object 74, which is one of the custom objects shown in FIG.

In the device ID display unit 300a, a device ID detail display unit 310 that displays details of device ID supplementary information related to a device ID, and a take-out / return status management information list display that displays a list of items related to take-out / return status management. Part 320.
The device ID detail display unit 310 can display information such as device ID (device identifier), device name, remarks, creator, and last updater.

Each display unit described above can be displayed through the web browser of the administrator terminal 50.

FIG. 7 is an explanatory diagram showing an example of the data structure of the custom object on the SaaS server in the take-out management system according to the first embodiment of the present invention.
In the data structure 400 in the take-out / return status management object, a first information storage unit 410 that defines information and object names to be displayed in a heading (display label) displayed as a custom tab, and a first information storage unit 410 that defines details of each information. 2 has an information storage unit 420.

In the second information storage unit 420, setting condition information such as item name, data type, number of characters, decimal point position, required items, unique, external ID, default value, other setting conditions, and remarks is defined for each record name. ing.
For example, when the record name is “device ID”, “Tool ID” is defined as the item name, “reference relationship” is defined as the data type, and “related destination: device” is defined as other settings.
For the record name “taker”, “TakeOutMechanic” is defined as the item name, “reference relationship” is defined as the data type, and “related party: mechanic” is defined as other settings.

(Local display screen)
FIG. 10 to FIG. 13 are explanatory diagrams illustrating an example of a local display screen in the take-out management system according to the first embodiment.
On the display screen 610 shown in FIG. 10, information 612 related to the mechanic ID and information 614 indicating normality or abnormality related to the taken-out article when passing through the gate are displayed.
During the reading of the mechanic ID and the device ID, information 632 related to the mechanic ID and information 634 indicating that the mechanic ID is being read are displayed on the display screen 630 shown in FIG.

If no abnormality (mismatch) is detected in at least one device ID as a result of reading, information 622 related to the mechanic ID and information 624 indicating normality are displayed on the display screen 620 shown in FIG. .
If an abnormality (mismatch) is detected in at least one device ID as a result of reading, information 642 related to the mechanic ID and information 644 indicating abnormality are displayed on the display screen 640 shown in FIG. The

(Queue information)
FIG. 14 is an explanatory diagram showing an example of queue implementation in the take-out management system according to the first embodiment.
As shown in FIG. 14, the queue information 720 is configured by, for example, a text file, and each queue information element 722 includes information indicating take-out / return, a mechanic ID, a device ID, a date, and the like.

(Log information)
FIG. 15 is an explanatory diagram illustrating an example of log implementation in the take-out management system according to the first embodiment.
As illustrated in FIG. 15, the log information 740 is configured by a text file, for example, and each log information element 742 includes a device ID, a date and time, a device name, and the like.

(Details of processing operation)
(Overall processing)
Next, the processing of each unit in the take-out management system having the above-described configuration can be realized as a method, and various processing procedures as an information processing method will be described with reference to FIGS. 8 and 9. FIG. 8 is a flowchart showing an example of a processing procedure in the take-out management system of FIG.

  The information processing operation according to the present embodiment is performed by a computer provided with a local control device that acquires information in a wireless electronic tag provided in an article taken out from a use site and manages the article. It is intended.

  In this information processing operation, as a basic operation procedure, a computer provided in a local control device logs take-out return information regarding take-out and return of the article based on information acquired from the wireless electronic tag at the use site. It is generated and stored as information (for example, step S105 shown in FIG. 8), and then the take-out return information is generated as queue information for transmitting to the SaaS management device at the use site and temporarily stored. (For example, step S109 shown in FIG. 8 and the like) Thereafter, the queue information is monitored and transmitted to the SaaS management apparatus via the communication network (for example, steps consisting of steps S201 to S206 shown in FIG. 9). be able to.

  Further, in this information processing operation, when performing the process of transmitting the queue information, if the queue information is empty in the local side transmission accumulation exchanging means for temporarily accumulating the queue information, the SaaS management device is When the queue information is transmitted, and the queue information is not empty, the queue information is temporarily stored in the local transmission storage and exchange means, and then transmitted at regular intervals (for example, the steps shown in FIG. 9). Step S201 to step S206).

The wireless electronic tag may include a first wireless electronic tag attached to a user at the site of use and a second wireless electronic tag attached to the article taken out by the user.
In this case, in this information processing operation, when the log information is generated, first acquisition information (for example, a mechanic ID) of the first wireless electronic tag and second acquisition information (for example, the second wireless electronic tag) The log information (for example, the file shown in FIG. 16) can be generated in association with the device ID.

  Further, when the article is returned, a collation determination is performed based on the log information when the article is taken out, and the log information is deleted when the coincidence is determined (for example, step shown in FIG. 8). S112).

  This will be described in detail below.

(Processing related to reading RFID)
First, when processing relating to reading of RFID is started, a computer (provided by the local control device) acquires information relating to the direction (carrying out / returning) of the sensor.
Further, the computer acquires information on the tag combination (device / mechanic) (step S101).

  Next, the computer determines whether the orientation of the sensor is “take-out” or “return” (step S102) <take-out / return determination processing step or take-out / return determination processing function>.

  Subsequently, when it is determined in step S102 that the orientation of the sensor is “takeout”, the computer reads the device ID and determines whether there is a device ID (step S103) <device identifier determination. Processing step or device identifier determination processing function>.

  Furthermore, when it is determined in step S103 that there is no device ID, the computer ends the process related to reading RFID.

  On the other hand, if it is determined in step S103 that there is a device ID, the computer subsequently reads the mechanic ID and determines whether there is a mechanic ID (step S104) <mechanical identifier determination processing. Step or mechanic identifier determination processing function>.

  If it is determined in step S104 that there is a mechanic ID, the computer subsequently performs processing for outputting a log file (step S105) <log file output processing step or log file output processing function>.

  If it is determined in step S104 that there is a mechanic ID, or if processing for outputting a log file is performed in step S105, the computer subsequently determines whether there is a queue (step S106). ) <Queue presence / absence determination processing step or queue presence / absence determination processing function>.

  If it is determined in step S106 that there is a queue, the computer subsequently performs processing for outputting the queue (step S109) <queue output processing step or queue output processing function>.

  On the other hand, if it is determined in step S106 that there is no queue, the computer performs a process of calling an API (step S107) <API call processing step or API call processing function>.

  Next, when the API is called, the computer performs processing for determining whether or not there is an API call error (step S108) <API call error determination processing step or API call error determination processing function>.

If it is determined in step S108 that there is an API call error, the computer subsequently performs processing for outputting the queue in step S109 <queue output processing step or queue output processing function>.
On the other hand, if it is determined in step S108 that there is no API call error, the computer ends the processing related to RFID reading.

(Queue monitoring process)
First, when the queue monitoring process is started, the computer checks the queue and determines whether there is a queue (step S201) <queue presence / absence determination processing step or queue presence / absence determination processing function>.

  If it is determined in step S201 that there is a queue, the computer subsequently performs a process of calling an API (step S203) <API call process step or API call process function>.

  On the other hand, if it is determined in step S201 that there is no queue, the computer performs processing for setting the sleep mode at regular intervals (step S202) <sleep processing step or sleep processing function>, and returns to step S201.

  Next, after step S203, the computer performs processing for determining whether or not there is an API call error (step S204) <API call error determination processing step or API call error determination processing function>.

  If it is determined in step S204 that there is an API call error, the computer subsequently performs processing for setting the sleep mode at regular intervals (step S205) <sleep processing step or sleep processing function>, and returns to step S201. .

  On the other hand, if it is determined in step S204 that there is no API call error, the computer performs processing to delete the queue (step S206) <queue deletion processing step or queue deletion processing function>, and returns to step S201.

As described above, according to the present embodiment, the first effect is that the operation at the use site can be continued when the SaaS service is stopped due to regular maintenance or failure.
There are two reasons for this.
First, operation data is held on the local side under the control of the control function.
Secondly, the message exchange delay synchronization is automatically taken under the control of the controller function.

  The second effect is that the development, maintenance, and operation in each distribution base and each factory become easy. The reason is that since the take-out management information database is centrally managed by SaaS, a database management server at each distribution base and each factory becomes unnecessary. Moreover, it is because it can respond easily to the needs of each site by customization on the SaaS side.

Each component (equipment ID) is associated with the mechanic ID, and the return log is held on the local side while using the QUE, thereby enabling check management at the time of return even in a state where the SaaS service cannot be connected.
Operation data can be stored locally using the controller function, and message exchange delay synchronization can be automatically performed. When the SaaS service is stopped due to periodic maintenance or failure, system operation at the site can be continued without stopping. .
It is possible to ensure service continuity while providing a low-cost service with the Saas service.

This system model does not need to be linked with the backbone system, and the business logic is almost the same at any location. In addition, it can be said that it is easy to introduce and deploy the system because it has a feature that some delay is allowed in the reflection to the database.
In addition, due to the characteristics of SaaS (Software As A Service) technology, which makes it easy to customize individual requirements and supports multiple languages, it is expected to expand not only in Japan but also overseas. In addition, a demo system can be easily constructed when changing business processes during introduction, so smooth system development is expected.

  Here, a part of each block in the block diagram shown in FIG. 1 has a software module configuration showing a state functionalized by a computer by executing various programs stored in an appropriate memory. May be.

  That is, the physical configuration is, for example, one or a plurality of CPUs (or one or a plurality of CPUs and one or a plurality of memories), etc., but the software configuration by each unit (circuit / means) is exhibited by the CPU by controlling the program. A plurality of functions are expressed as components by a plurality of units (means).

  When the CPU dynamically expresses a dynamic state (a state in which each procedure constituting the program is executed) executed by the program, each unit (means) is configured in the CPU. In a static state in which the program is not executed, the entire program (or each program part included in the configuration of each unit) that realizes the configuration of each unit is stored in a storage area such as a memory.

  The description of each part (means) described above can be interpreted as a computer functionalized by a program together with the function of the program, or a plurality of functions permanently functioning by specific hardware. It can also be interpreted that the device comprising the electronic circuit block is described. Therefore, these functional blocks can be realized in various forms by hardware only, software only, or a combination thereof, and is not limited to any one.

  In addition, each unit may be configured as a device including a dedicated computer capable of communication, and the system may be configured by each of these devices. Conversely, a system in which each unit is configured as a single device may be used.

[Other variations]
Also, although the apparatus and method according to the present invention have been described according to some specific embodiments thereof, the embodiments described in the text of the present invention can be used without departing from the spirit and scope of the present invention. Various modifications are possible.

  For example, in the above embodiment, the controller function, the local operation data holding function, and the cooperation interface function are arranged. However, all these take-out information and return information are transferred from the RFID control process to the SaaS management system without arranging these functions. The same can be achieved by direct output.

  For example, the number, position, shape, and the like of the constituent members are not limited to the above-described embodiment, and can be set to a suitable number, position, shape, and the like in practicing the present invention. That is, in the above-described embodiment, the case where there is one local control device is shown as an example of the system configuration, but the present invention does not limit the number of these devices.

  For example, as a communication structure between a wireless electronic tag and an acquisition device (means) including a wireless antenna, various types such as communication using a non-contact IC, wireless LAN, and Bluetooth (registered trademark) can be cited.

In the case of a non-contact type IC, examples of the wireless electronic tag include an RFID (Radio Frequency ID Enhancement) tag. At this time, as an acquisition device, for example, an RFID reader including a receiving antenna can be cited.
The RFID tag standard is a first type in which a frequency range of LF (Low Frequency) is 125 to 134 KHz and a communication distance is about 1 to 100 cm, a frequency band of HF (High Frequency) is 13.56 MHz and a communication distance is about 1 m. The second type of UHF (Ultra HF) has a frequency of 860 to 960 MHz and a communication distance of about 7 m, a microwave usage frequency of 2.45 GHz and a communication type of about 4 m and so forth. Things are assumed.
Furthermore, any type of active tag that has a built-in battery, emits radio waves by itself, and returns tag information to the reader, and a passive tag that does not have a built-in battery and returns tag information to the reader using radio waves from the reader as energy It may be. In the case of an active tag, the used frequency band is 300 MHz and the communication distance is about 10 to 20 m.
For this reason, the number of antennas and RFID tag readers can be appropriately changed according to the communication distance.

  In addition, as a communication structure between a wireless electronic tag and an acquisition device equipped with a wireless antenna, etc., ZigBee (first type of use frequency 2.4 GHz, second type of use frequency 915 MHz, third type of use frequency 868 MHz, Various wireless standards such as a communication distance of about 9 m to about 69 m), UWB (a use frequency of about 3.1 GHz to about 10.69 GHz, a communication distance of about 20 or less), and the like. In other embodiments, these various communication structures may be employed.

  Other configurations, other steps or functions, and the effects thereof are the same as those in the above-described embodiment. In the above description, the operation content of each step described above, the constituent elements of each unit, and the functions thereof may be programmed (software program) and executed by a computer.

  The present invention can be used for all computer systems.

It is a block diagram which shows an example of the whole structure of the taking-out management system by the 1st Embodiment of this invention. It is explanatory drawing for demonstrating an example of the operation | movement outline | summary in the taking-out management system of FIG. It is explanatory drawing which shows an example of a structure of the custom object on the SaaS server in the taking-out management system by the 1st Embodiment of this invention. FIG. 4 is an explanatory diagram illustrating an example of a configuration of a custom tab that expands the custom object of FIG. 3 on a display screen. FIG. 4 is an explanatory diagram illustrating an example of a configuration of a custom tab that expands the custom object of FIG. 3 on a display screen. FIG. 4 is an explanatory diagram illustrating an example of a configuration of a custom tab that expands the custom object of FIG. 3 on a display screen. It is explanatory drawing which shows an example of the data structure of the custom object on the SaaS server in the taking-out management system by the 1st Embodiment of this invention. It is a flowchart which shows an example of the process sequence in the take-out management system by the 1st Embodiment of this invention. It is a flowchart which shows an example of the process sequence in the take-out management system by the 1st Embodiment of this invention. It is explanatory drawing which shows an example of the display screen of the local side in the taking-out management system by the 1st Embodiment of this invention. It is explanatory drawing which shows an example of the display screen of the local side in the taking-out management system by the 1st Embodiment of this invention. It is explanatory drawing which shows an example of the display screen of the local side in the taking-out management system by the 1st Embodiment of this invention. It is explanatory drawing which shows an example of the display screen of the local side in the taking-out management system by the 1st Embodiment of this invention. It is explanatory drawing which shows an example of mounting of the queue in the taking-out management system by the 1st Embodiment of this invention. It is explanatory drawing which shows an example of the implementation of the log in the taking-out management system by the 1st Embodiment of this invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Take-out management system 2 Local side system 2a RFID control system 2b On-site system 2c Local side control apparatus 3 Management side system (SaaS management apparatus)
10 RFID control process 12 Controller function (control means)
14 Local operation data retention function (local operation data retention means)
16 take-out return log information storage unit 18 RFID manager 20 local side transmission accumulation exchange function (QUE) (local side transmission accumulation exchange means)
30 RFID gate (acquisition device)
32 RFID reader (reading device)
34 RFID antenna 36a, 36b Human sensor (detection means)
38 Patlite (notification means)
50 administrator terminal 62 SaaS management system (SaaS management database server)
64a SaaS side transmission storage exchange function

N communication network

Claims (12)

A take-out management system for acquiring information in a wireless electronic tag provided in an article taken out from a use site and managing the article,
A SaaS management device for centrally managing take-out return information regarding take-out and return of the article at each use site;
It is installed at each use site so as to be able to communicate with the SaaS management device via a communication network, and generates and temporarily holds take-out return information regarding take-out and return of the article based on acquired information acquired from the wireless electronic tag. A local control unit;
A take-out management system characterized by including In the take-out management system according to claim 1,
The local control device is:
Local operation data holding means for storing the take-out return information as log information;
A local side transmission accumulation exchanging means for temporarily accumulating the take-out return information as queue information for transmitting to the SaaS management device;
The take-out return information is generated as the log information and accumulated in the local-side operation data holding unit, and the take-out return information is generated as the queue information in the local-side transmission accumulation / exchange unit, and the local-side operation data holding unit And control means for controlling the local-side transmission storage exchange means,
A take-out management system characterized by including In the take-out management system according to claim 2,
The control means includes
When the queue information is monitored and the queue information of the local transmission storage and exchange means is empty, the queue information is transmitted to the SaaS management device, and when the queue information is not empty, the local information A take-out management system, wherein the queue information is temporarily stored in the side transmission storage and exchange means, and then transmitted at regular intervals. In the take-out management system according to claim 3,
The wireless electronic tag includes a first wireless electronic tag attached to a user at the usage site, and a second wireless electronic tag attached to the article taken out by the user,
The control means includes
The take-out management system, wherein the log information is generated by associating first acquisition information of the first wireless electronic tag and second acquisition information of the second wireless electronic tag. In the take-out management system according to claim 4,
The control means includes
A take-out management system, wherein when the article is returned, a collation determination is made based on the log information when the article is taken out, and the log information is deleted when a match is determined. In the take-out management system according to claim 5,
A take-out management system further comprising an administrator terminal installed at the use site and capable of acquiring and updating information of the SaaS management device. A local-side control device installed at each use site so as to be communicable via a communication network with a SaaS management device that centrally manages take-out return information regarding take-out and return of items taken out from the use site,
Local operation data holding means for storing the take-out return information as log information;
A local side transmission accumulation exchanging means for temporarily accumulating the take-out return information as queue information for transmitting to the SaaS management device;
The take-out return information is generated as the log information and accumulated in the local-side operation data holding unit, and the take-out return information is generated as the queue information in the local-side transmission accumulation / exchange unit, and the local-side operation data holding unit And control means for controlling the local-side transmission storage exchange means,
A local-side control device. An information processing method in which a computer performs processing for acquiring information in a wireless electronic tag provided in an article taken out from a use site and managing the article,
Based on the acquisition information from the wireless electronic tag, the computer takes out and returns information related to taking out and returning it as log information at the site of use and stores it,
Subsequently, the take-out return information is generated as queue information for transmitting to the SaaS management device by the computer at the use site, and temporarily stored.
Thereafter, the queue information is monitored by the computer and transmitted to the SaaS management device via a communication network.
An information processing method characterized by the above. The information processing method according to claim 8,
When performing the process of transmitting the queue information,
When the queue information is vacant in the local transmission storing and exchanging means for temporarily storing the queue information, the queue information is transmitted to the SaaS management device, and when the queue information is not empty, the local side An information processing method, wherein the queue information is temporarily accumulated in a transmission accumulation exchanging means, and then transmitted at a predetermined interval. The information processing method according to claim 9,
The wireless electronic tag includes a first wireless electronic tag attached to a user at the usage site, and a second wireless electronic tag attached to the article taken out by the user,
When generating the log information,
The log information is generated by associating first acquisition information of the first wireless electronic tag and second acquisition information of the second wireless electronic tag. The information processing method according to claim 10,
An information processing method, wherein when the article is returned, a collation determination is made based on the log information when the article is taken out, and the log information is deleted when a match is determined. The SaaS management device that centrally manages take-out return information related to take-out and return of items taken out from the use site and the computer provided with the local control device installed at each use site so as to be able to communicate via the communication network have various functions. A program for a local control device that can be realized,
A first processing function for generating and storing the take-out return information as log information;
A second processing function for generating and temporarily storing the take-out return information as queue information for transmitting to the SaaS management device;
A third processing function for performing processing of monitoring the queue information and transmitting it to the SaaS management device via a communication network;
A program for a local control device, which causes a computer to implement a function including:

Images