Classifications

• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q10/00—Administration; Management
  • G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
  • G06Q10/087—Inventory or stock management, e.g. order filling, procurement or balancing against orders

Definitions

• IT assets include computers, printers, peripherals, personal digital assistants, and a variety of similar devices. Maintaining and tracking these assets can be challenging, particularly for large organizations. The problem may be further compounded as the IT assets are used by a large number of employees that may move among a variety of different facilities, beyond corporate premises, and around the globe. [0002] Due to their ease of portability, IT assets may be frequently misplaced or even stolen. Millions of dollars are spent by organizations either trying to locate these assets, or to purchase additional assets as replacements. Enterprises also typically spend a significant amount of time and expense provisioning these devices with software and appropriate information because of the manual processes involved. When an asset reaches retirement age, it may be necessary to "find" the asset in order to reallocate its software to avoid unnecessary license and purchase costs. Even an asset that hasn't been stolen costs money.
• a detection region for radio frequency identifier (RFID) signals is monitored, and any RFID signals associated with IT assets within the detection region are sensed.
• a detected RFID signal is analyzed to obtain identifying information regarding the IT asset.
• the identifying information is formatted for storage.
• the RFID signal may be further analyzed to determine whether the IT asset complies with a local (or location-specific) policy specification associated with the IT asset, and a notification of noncompliance may be issued if the IT asset does not comply with the local policy specification.
• Figure 1 illustrates an exemplary environment for implementing techniques to discover and track information technology (IT) assets using radio frequency identifier (RFID) tagging.
• Figure 2 is a block diagram of an exemplary computing device and a tool executable on the computing device to perform discovery and tracking of IT assets using RFID tagging in.
• IT information technology
• RFID radio frequency identifier
• Figure 3 is a flow diagram of an exemplary process for IT asset discovery.
• Figure 4 is a flow diagram of another exemplary process for IT asset discovery.
• Figure 5 is an exemplary system for management of IT assets using RFID tagging.
• Figure 6 is a flow diagram of an exemplary process of discovering and tracking IT assets using the exemplary system of Figure 5.
• Figure 7 is another exemplary system for monitoring IT assets using RFID tagging.
• Figure 8 is a flow diagram of an exemplary process of monitoring IT assets using the exemplary system of Figure 7.
• the present disclosure describes use of information provided by a radio frequency identifier (RFID) tag located on an IT asset to discover, track, and provision the IT asset.
• RFID radio frequency identifier
• the RFID tag is placed on the IT asset by a provider, such as an original equipment manufacturer, distributor, supplier, or retailer, prior to delivery to a customer.
• the provider can also send the customer a list (e.g. a purchase order or the like) of the tags as they correlate to the items ordered.
• the IT asset shows up at the customer's facility (e.g. a receiving and loading area)
• the customer may use an RFID reader to detect the IT asset, and correlate that device into an IT asset manager.
• the IT asset manager may also access a provisioning policy so that once the IT asset is coupled to a network, the IT asset can automatically receive the software/applications that it needs as specified by the provisioning policy.
• the provisioning policy may be previously stored in (or otherwise accessible to) the IT asset manager, or alternately, may be provided by the RFID tag located on the IT asset. In this way, customers can track and provision IT assets accurately and efficiently, dramatically reducing the costs of managing and processing IT assets.
• RFID radio frequency identifier
• the RFID information storage mechanism attached to the object may be referred to as a tag, transponder, electronic label, code plate, and various other terms. Although transponder is technically the most accurate, the term most commonly used for these devices throughout this application is the term "tag.”
• Data may be contained on the RFID tag in one or more bits for the purpose of providing identification and other information relevant to the IT asset to which the RFID tag is attached.
• RFID devices may incorporate the use of electromagnetic or electrostatic coupling in the radio frequency portion of the spectrum to communicate to or from an RFID tag through a variety of modulation and encodation schemes.
• EPC Electronic Product Code
• FIG 1 illustrates an exemplary environment 100 for implementing techniques to discover and track information technology (IT) assets using radio frequency identifier (RFID) tagging.
• the environment 100 includes an IT asset 102 that is associated with an RFID tag 110.
• the RFID tag 110 may be affixed to the IT asset 102, or embedded in the electronics, or otherwise associated with the IT asset 102 to uniquely identify that IT asset 102.
• the IT asset 102 is illustrated as a portable computer.
• the IT asset 102 may be essentially any number of asset types, including computing devices, peripherals, networking devices, communication devices, and the like, as well as individual components of such devices.
• An RFID reader 112 is configured to receive signals 114 from the RFID tag 110 within a detection region 116.
• the term "RFID reader” is intended to include any device that receives RFID signals from the RFID tag 110.
• the RFID reader 112 may extract and separate information from the RFID signals, including differentiating format definition and error management bits.
• digital electronics within the RFID reader 112 perform the actual reading function. These read electronics may also interface to an integral display and may provide a parallel or serial communications interface to a host computer or industrial controller, as described below.
• the RFID reader 112 includes a transmitter/receiver pair (or transceiver).
• the RFID reader 112 sends the information extracted from the RFID tag 110 via one or more networks 118 to a platform 120.
• the platform 120 is illustrated in Figure 1 as a server, but this is merely for representation.
• the platform 120 may be implemented in any number of suitable ways, including as a desktop computing device, a mainframe, a cluster, a portable computer, and so forth.
• An exemplary architecture of the platform 120 is illustrated below with reference to Figure 2.
• An IT asset management tool 130 operates on the platform 120 and provides information to a user via a user interface 122. Using the IT asset management tool 130 and the other components of the exemplary environment 100, the user may discover and track the location of the IT asset 102 as it moves within the detection region 116.
• the IT asset mgmt tool 130 resides on a server (e.g.
• Embodiments of techniques in accordance with the present disclosure may significantly improve an organization's ability to efficiently discover and track IT assets, saving the organization considerable expense associated with these activities and also with the replacement of lost IT assets. Further embodiments may also substantially improve the process of provisioning IT assets with the appropriate software and configuration information.
• FIG. 2 illustrates various components of an exemplary system 200 that includes the platform 120 and the IT asset management tool 130 executable on the platform 120.
• the platform 120 includes a hardware layer 202 and an RFID infrastructure layer 204.
• An EPC reader 206 of the hardware layer 202 receives incoming information (or signals) 114 from the RFID reader 112, and provides the information 114 to an EPC component 214 of the RFID infrastructure layer 204.
• the EPC component 214 interprets the information to determine the relevant characteristics and identifying information regarding the IT assets 102 detected by the RFID reader 112.
• the hardware layer 202 may also include a current devices reader 208, a next generation devices reader 210, and one or more additional sensors 212 that are configured to receive the information 114 from the RFID reader 112 regarding other current devices, next generation (or future) devices, or any other additional device signals, respectively.
• the current devices reader 208, the next generation devices reader 210, and the sensors 212 may communicate with one or more custom provider components 216 of the RFID infrastructure layer 204.
• the EPC reader 206 (and the custom provider components 216) communicate with the IT asset management tool 130 via a device service provider interface (DSPI) 218.
• DSPI device service provider interface
• the IT asset management tool 130 includes an event processing engine 222 that receives the incoming information (or signals) 114 from the DSPI 218, and stores the information to an event database 220. More specifically, the event processing engine 222 may process and interpret the information from the DSPI 218 (i.e. from the RFID reader 112), and translate the information into meaningful events, prior to storage in the event database 220, or alternately, the raw information from the DSPI 218 (or the RFID reader 112) may be stored in the event database 220 for subsequent processing and interpretation by the IT asset management tool 130.
• the event processing engine 222 may process and interpret the information from the DSPI 218 (i.e. from the RFID reader 112), and translate the information into meaningful events, prior to storage in the event database 220, or alternately, the raw information from the DSPI 218 (or the RFID reader 112) may be stored in the event database 220 for subsequent processing and interpretation by the IT asset management tool 130.
• a device management component 224 exchanges information with the event processing engine 222 and the event database 220, and may perform higher level IT asset management functions, such as reconciling arrival of IT assets with purchase orders, checking a status of an IT asset against an expected or authorized status, maintaining an inventory of IT assets, issuing warnings or alerts for IT assets that may be in non- compliance with company policies and procedures, and any other desired higher level management functions.
• the IT asset management tool 130 may, in turn, communicate information via one or more RFID infrastructure object models (OMs), application programming interfaces (APIs), and adapters 226 to existing modules 230 that may perform a variety of different functions with such information.
• OMs RFID infrastructure object models
• APIs application programming interfaces
• adapters 226 to existing modules 230 that may perform a variety of different functions with such information.
• the IT asset management tool 130 may communicate information to a business process management tool 232, such as the BizTalk tool available from the Microsoft Corporation of Redmond, Washington. Information may also be communicated to a financial, supply chain, and customer management component 236, such as the Microsoft Dynamics tool, or to a customized, application-specific partner solution 234 that may utilize the IT asset information in any suitable manner.
• a business process management tool 232 such as the BizTalk tool available from the Microsoft Corporation of Redmond, Washington.
• Information may also be communicated to a financial, supply chain, and customer management component 236, such as the Microsoft Dynamics tool, or to a customized, application-specific partner solution 234 that may utilize the IT asset information in any suitable manner.
• the components of the IT asset management tool 130 may be implemented on a single platform 120 as shown in Figure 2, or alternately, these components may be distributed over a plurality of devices.
• the functionalities of one or more of the components of the IT asset management tool 130 may be combined into one or more utilities that perform the desired functionalities.
• the system 200 shown in Figure 2 advantageously provides a modular, flexible solution that enables the "plugability" of any desired device/reader 112 into the RFID infrastructure 204, and the incorporation of any desired programmatic interfaces 226 to discover, collect, process, filter, and use the RFID data.for any desired purpose.
• the device management component 224 may be an existing process management package.
• the device management component 224 may be a systems management package known as the System Center Configuration Manager (SCCM) commercially available from Microsoft.
• SCCM System Center Configuration Manager
• any suitable embodiments of the device management component 224 may be employed.
• program modules executed on the components of the platform 120 include routines, programs, objects, components, data structures, etc., for performing particular tasks or implementing particular abstract data types. These program modules and the like may be executed as a native code or may be downloaded and executed such as in a virtual machine or other just- in-time compilation execution environments. Typically, the functionality of the program modules may be combined or distributed as desired in various implementations. [0031] An implementation of these modules and techniques may be stored on or transmitted across some form of computer-readable media. Computer-readable media can be any available media that can be accessed by a computer.
• Computer-readable media may comprise computer storage media that includes volatile and non- volatile, removable and nonremovable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data.
• Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium, including paper, punch cards and the like, which can be used to store the desired information and which can be accessed by a computer.
• Figure 2 also depicts an exemplary RFID information unit 250 provided by the RFID tag 110 for use by the IT asset management tool 130.
• a first portion 252 of the RFID information unit 250 includes information descriptive of the IT asset 102 with which the RFID tag 110 is associated.
• the first portion 252 may include a manufacturer name, model number, serial number, media access control (MAC) address, Universally Unique Identifier (UUID), Globally Unique Identifier (GUID), configuration information, component information, and any other desired information descriptive of the IT asset 102.
• the descriptive information of the first portion 252 is consistent with the data and meta-data models of the Services Modeling Language Platform (including the Common Model Library) currently being developed by various organizations, and under consideration for standardization by the Distributed Management Task Force of Portland, Oregon.
• a second portion 254 of the RFID information unit 250 may include information relevant to the owner or purchaser of the IT asset 102, such as the name of the owner, name of the intended user, intended location of use, and any other desired owner-related information.
• the second portion 254 (or the first portion 252) may include a provisioning policy 256 which may be used for provisioning the IT asset 102, as described more fully below.
• an event occurs when incoming data from an RFID tag registers with an RFID reader that meets this data model and has actual data in the above-referenced core physical asset fields (e.g. MAC Address, etc).
• FIG. 3 shows an exemplary process 300 for IT asset discovery using RFID tagging.
• the process 300 is illustrated as a collection of blocks in a logical flow graph, which represents a sequence of operations that can be implemented in hardware, software, or a combination thereof.
• the blocks represent computer instructions that, when executed by one or more processors, perform the recited operations.
• the process 300 is described with reference to the exemplary environment 100 shown in Figure 1, and the exemplary system 200 shown in Figure 2.
• the process 300 generally includes an asset discovery branch 310 and an RFID data gathering branch 340.
• the activities associated with the asset discovery branch 310 and the RFID data gathering branch 340 may be performed consecutively or concurrently, or combinations of both.
• the RFID data gathering branch 340 may be initiated prior to the asset discovery branch 310 in order to populate the event database 220 ( Figure 2) with RFID data from the IT assets of the organization.
• an RFID data gathering activity is activated at 342.
• a determination is made whether to perform a data update (e.g. by the RFID infrastructure 204), such as the passage of a predetermined time increment or other suitable update condition.
• RFID data is received from the IT assets of the organization at 346, and are stored to the RFID database 220 at 348.
• the RFID data gathering branch 340 may also return to the data update determination at 344 and continue to gather RFID data and store the RFID data in the event database 220 for future access.
• an RFID discovery mode of the IT asset management tool 130 is activated at 312 (e.g. by the asset manager 240). In some embodiments, this may be accomplished by a user inputting appropriate commands via an I/O device 206 of the platform 120. Alternately, the RFID discovery mode may be activated automatically by appropriate system management software, such as during a periodic data collection or routine inspection activity on the IT assets of an organization.
• the user or system management software may specify one or more portions of the organization's IT environment on which to perform IT asset discovery. For example, it may only be necessary or desirable to perform IT asset discovery within selected portions of the organization (e.g. receiving and loading areas, laboratories, research divisions, manufacturing facilities, etc.).
• the IT asset discovery may be performed over the entire organization.
• filtering for one or more tag types of interest is performed.
• various RFID signals (or RFID tag types) may be received that are not of interest to the IT asset discovery process 300.
• a system management software may perform relatively frequent asset discoveries of an organization's RFID tags associated with one type of IT asset (e.g. mobile IT assets), and less frequent asset discoveries of RFID tags associated with another type of IT asset (e.g.
• the IT asset discovery may be performed to study general movements of IT assets that have occurred in the past, to determine the movement of a particular IT asset during a particular period of time in the past, or some other type of IT asset discovery that only requires historical data. If it is determined that historical data is sufficient at 318, then the event database 220 is accessed (e.g.
• the process 300 proceeds to the RFID data gathering branch 340 to perform a current or up-to-the-moment RFID data retrieval from the IT assets at 346, which is then stored in the RFID database 220 at 348.
• the RFID data gathering branch 340 determines that it should return to the asset discovery branch 310, and at 320, the event database 220 is accessed to receive the specified or desired RFID discovery data.
• the asset discovery branch 310 determines whether asset discovery is complete. If not, the process 300 returns to the specification activities at 314, and the above-described activities may be repeated as desired. Alternately, if asset discovery is complete at 322, the process 300 may end or continue to other desired operations.
• FIG. 4 is a flow diagram of an exemplary process 400 for IT asset discovery in accordance with another embodiment of the invention.
• the process 400 includes an asset discovery branch 410 and an RFID monitoring branch 440.
• the RFID monitoring branch 440 "pushes” the RFID data to the asset discovery branch 410.
• An RFID data monitoring is activated at 442.
• a determination is made whether an event has been detected, such as by the RFID reader 112 receiving an RFID information unit 250 and providing corresponding RFID data to the RFID platform 210.
• the RFID monitoring branch 440 continues to monitor for RFID data until an event is detected.
• RFID data is received from the IT assets at 446, and may be stored to the event database 220 at 448.
• an RFID discovery mode of the IT asset management tool 130 is activated at 412.
• IT asset discovery specifications are defined, such as by the user, the system management software, or both.
• the specifications may include, for example, one or more specified portions of the organization's IT environment on which to perform IT asset discovery (e.g. receiving and loading areas, laboratories, etc.), and filtering options, such as types of IT assets (e.g. laptops, etc.), event types (e.g. an IT asset passing by an RFID reader 112 positioned on a peripheral edge of the IT environment, etc.), or any other desired asset discovery specifications.
• IT asset discovery e.g. receiving and loading areas, laboratories, etc.
• filtering options such as types of IT assets (e.g. laptops, etc.), event types (e.g. an IT asset passing by an RFID reader 112 positioned on a peripheral edge of the IT environment, etc.), or any other desired asset discovery specifications.
• the RFID monitoring branch 440 compares the RFID event data (received at 446) with the asset discovery specifications provided by the asset discovery branch (updated at 418). If the RFID event data satisfies the specifications at 452, then the RFID event data are provided to the IT asset manager at 454. Otherwise, the RFID monitoring branch 440 returns to monitoring for an event at 444.
• the asset discovery branch 410 receives the RFID event data, and may perform desired operations and analyses on the RFID event data, at 420.
• the RFID event data may be displayed to the user via the user interface 122 ( Figure 1), output to an electronic or printed report, identified to the system management software or other software utilities, or any other desired operations.
• the asset discovery branch 410 determines whether asset discovery is complete. If not, the process 400 returns to the definition of asset discovery specifications at 414, and the above-described activities may be repeated as desired. Alternately, if asset discovery is complete at 422, the process 400 may end or continue to other desired operations.
• RFID tags can be placed on IT assets (e.g. by an original equipment manufacturer, supplier, retailer, etc.) prior to shipment to a customer.
• the customer may also receive a list of the RFID tags as they correlate to the IT assets ordered.
• one or more RFID readers may detect the IT asset, store the corresponding event data into the event database, and correlate that IT asset into the customer's asset manager (e.g. SCCM).
• SCCM customer's asset manager
• the IT asset can also be registered and reconciled with the list or purchase order in a purchasing/asset management application.
• Figure 5 is an exemplary system 500 for management of IT assets using RFID tagging in accordance with another embodiment of the invention.
• the system 500 includes an RFID reader 512 configured to receive signals 514 from one or more RFID tags 510 located on RFID assets 502 within a detection region 516.
• the RFID reader 512 is coupled to an inventory system 520 via a network 518.
• the inventory system 520 includes an RFID platform component 530, an event component 540, a purchasing component 550, and an asset management component 560.
• An IT asset management tool 570 operates on the inventory system 520, and in this particular embodiment, on the event component 540, and enables the inventory system 520 to manage the IT assets 502 within the detection region 516, as described below.
• FIG. 6 is a flow diagram of an exemplary method 600 of managing IT assets using the exemplary system 500 of Figure 5.
• an order is placed by an organization for an IT asset, such as a laptop 502a, a computer 502b, a personal digital assistant 502c, a printer 502d, or any other desired type of IT asset.
• the order may be accomplished by a user using the purchasing component 550 of the inventory system 520, and may include generating a purchase order for the desired IT asset.
• the order is received by an IT asset provider at 604.
• the IT asset provider may be an outside vendor or OEM, or an in-house department or individual responsible for providing IT assets to users within the organization, or any other type of IT asset provider.
• the IT asset provider prepares the IT asset(s) for delivery to the purchaser. This may include affixing an RFID tag 510 to each IT asset, and encoding the RFID tag 510 with relevant information corresponding to the organization's order.
• the RFID tag 510 may include information descriptive of the IT asset 502 (e.g. manufacturer, model, serial number, MAC address, UUID, GUID, configuration, etc.), and information specific to the order (e.g. owner, intended user, intended location, order date, requester, provisioning policy, etc.).
• the RFID tag 510 may be pre-encoded by the manufacturer with information specific to the IT asset 502, and the IT asset provider may prepare the IT asset for delivery by further encoding the RFID tag 510 with information specific to the order placed at 602.
• the IT asset 502 arrives to the purchaser at 610. More specifically, as shown in Figure 5, the IT asset 502 arrives within the detection region 516 and is detected by the RFID reader 512.
• the detection region 516 may include a receiving area, a loading dock, a mail room, or any other suitable area.
• the RFID reader 512 decodes the signals 514 from the RFID tag 510 and transmits appropriate information based on the decoded signals 514 to the inventory system 520, notifying the inventory system 520 of the arrival of the IT asset 502.
• the inventory system 520 may analyze the data from the RFID reader 512 and update records accordingly. More specifically, in the embodiment shown in Figure 5, the event component 540 of the inventory system 520 may use the IT asset management tool 570 to analyze the information from the RFID reader 512, interpret and reformat this information (if necessary), and if an event of interest is determined (such as arrival of the IT asset 502), provide this information to the purchasing component 550 and the asset management component 560.
• the IT asset management tool 570 may perform the desired activities and functions as described above with reference to the IT asset management tool 130.
• the event component 540 may use the IT asset management tool 570 to compare the data received from the RFID platform component 530 with predetermined specifications (such as the order for IT assets placed at 602). If the data satisfies the specifications, then the event component 540 may notify the purchasing component 550 and the asset management component 560 of the arrival of the IT asset 502. The purchasing component 550 may reconcile the order records to reflect and document that the order has been satisfied (or not). Similarly, the asset management component 560 may update appropriate records to reflect the arrival, location, configuration, responsible user, and other desired details regarding the IT asset 502.
• the inventory system 520 also provisions the IT asset 502 at 616. For example, upon updating the appropriate records to reflect the presence and configuration of the IT asset 502 (at 614), a component of the inventory system 520, such as the asset management component 560, may access a provisioning policy associated with the particular IT asset 502.
• the provisioning policy is located in a memory of the inventory system 520. Alternately, as described above with respect to Figure 2, the provisioning policy may be obtained from the RFID tag 110 associated with the IT asset 502.
• the asset management component 560 (or other component of the inventory system 520) identifies that the IT asset 502 belongs to a certain cost center or department within the requesting organization.
• the inventory system 520 determines that the IT asset 502 is among a collection of assets and components that are intended to receive a specific set of software and configuration information (i.e. a specific provisioning policy).
• the asset management component 560 may identify the IT asset 502 to a provisioning component, which may be a part of the inventory system 520 (such as the event component 530), or which may be a separate, third party component.
• the asset management component 560 may provide a MAC address or other suitable identifier obtained from the RFID tag 510 associated with the IT asset 502 to a provisioning component, such as a
• Preboot execution (PxE) server along with an associated provisioning policy.
• PxE Preboot execution
• the inventory system 520 contacts the PxE server, boots from this server, and receives its policy instructions, and then provisions the IT asset 502 with the software and settings as specified by the provisioning policy.
• FIG. 7 is an exemplary system 700 for monitoring IT assets using RFID tagging in accordance with yet another embodiment of the invention. It will be appreciated that many of the components of the monitoring system 700 are similar (or identical) to the components of the management system 500 described above with reference to Figure 5. For the sake of brevity, the complete description of such common components will not be repeated, and only significant differences between the monitoring system 700 and the management system 500 will be described in detail.
• the monitoring system 700 includes a second RFID reader 712 configured to monitor a second detection region 716. When one or more of the IT assets 502 enters the second detection region 716, the signals 514 are received by the second RFID reader 712 and transmitted to the inventory system 520 via the network 518.
• the second RFID reader 712 may also receive second RFID signals 714 from a second RFID tag 710 located on a user 702.
• the first RFID reader 512 may also receive the second RFID signals 714 from the second RFID tag 710 when the user 702 is present within the first detection region 516.
• one or more satellites 730 could be configured to receive signals from one or more of the RFID readers 512, 712 (e.g. satellite 730a), or directly from one or more of the RFID tags 510, 710 (e.g. satellite 730b), and to communicate this information to the inventory system 520, such as to a receiver 732 in operative communication with the event component 540.
• the RFID tags 510, 710 may be "active" tags that broadcast with sufficient power to enable satellite monitoring.
• global location awareness tools like assisted Global Positioning (or GPS), broadband networks, etc., the locations of the IT assets 502 may be monitored and determined via triangulation on a worldwide scale.
• a method 800 of monitoring IT assets using the monitoring system 700 is shown in Figure 8.
• one or more IT assets 502 are detected and monitored within the first detection region 516.
• the user 702 may enter the first detection region 516 and be detected by the first RFID reader 512 at 804.
• an RFID reader other than the first RFID reader 512 may be used to detect the presence of the user 702 within the first detection region 512.
• the second RFID tag 710 may be affixed to an identification badge worn by the user 702, and access to the first detection region 512 may require the user 702 to scan the identification badge (i.e. the second RFID tag 710) through a scanner to gain entry.
• the absence of the IT asset 502 from the first detection region 512 may be detected by the first RFID reader 512.
• the user 702 may exit from the first detection region 512 carrying the IT asset 502a, causing the RFID tag 510a on the IT asset 502a to stop registering with the first RFID scanner 512, and the absence of the IT asset 502a to be noted by the IT asset management tool 770.
• the absence of the user 702 from the first detection region 512 may also be detected (e.g. by the first RFID reader 512, a badge reader, etc.), and the corresponding times of these events recorded.
• a record of the absence of the IT asset 502a may be generated at 808.
• a message in the inventory system 520 such as a Desired Configuration Management state message in the asset management component 570, that the IT asset 502a is no longer in policy.
• the presence of the RFID asset 502a within the second detection region 716 may be detected and recorded at 810.
• the presence of the user 702 may also be detected (and recorded).
• the movements of the IT asset 502a (and the user 702) may continue to be monitored and recorded as the IT asset 502 (and user 702) move into and out of monitored regions.
• the monitoring system 700 may be expanded to include any number of monitored regions, enabling the movements of the IT asset 502a (and user 702) to be continuously monitored and updated as they move about the organization.
• the movement of the IT asset 502a may be monitored anywhere there is coverage by satellites 730.
• the records of the movements (presence, absence, or both) of the IT asset 502a and the user 702 may be analyzed, and if necessary, appropriate action may be taken at 814.
• the inventory system 520 may take various actions, such as sending a message to the user 702 advising that the removal of the IT asset 502a is against policy, alerting a party responsible for monitoring the IT asset 502a of the movement of the IT asset 502a, or any other suitable action. It will be appreciated that, in some embodiments, the appropriate action may also include remaining passive and continuing to monitor and record the movements of the IT asset 502a.
• analysis of the movement records of the IT asset(s) 502 may reveal a variety of information, including last known direction of movement, point of departure from an organization's monitored environment, time of absence from the organization's monitored environment, users present within the monitored environment during times of interest, or other desired information.
• last known direction of movement point of departure from an organization's monitored environment
• time of absence from the organization's monitored environment users present within the monitored environment during times of interest, or other desired information.
• a possible correlation of the RFID tag 710 of the user 702 with the IT asset 502a can be assessed to better determine the last known person that may have had the IT asset 502a.
• a party responsible for the IT asset 502a may verify that the IT asset 502a remains within the last known detection region, such as by using a hand scanner to perform a scan of the RFID signals within the last known detection region.

Landscapes

• Business, Economics & Management (AREA)
• Economics (AREA)
• Engineering & Computer Science (AREA)
• Quality & Reliability (AREA)
• Tourism & Hospitality (AREA)
• Finance (AREA)
• Entrepreneurship & Innovation (AREA)
• Human Resources & Organizations (AREA)
• Marketing (AREA)
• Operations Research (AREA)
• Accounting & Taxation (AREA)
• Strategic Management (AREA)
• Development Economics (AREA)
• Physics & Mathematics (AREA)
• General Business, Economics & Management (AREA)
• General Physics & Mathematics (AREA)
• Theoretical Computer Science (AREA)
• Management, Administration, Business Operations System, And Electronic Commerce (AREA)
• Storage Device Security (AREA)
• Burglar Alarm Systems (AREA)

Priority Applications (3)

Applications Claiming Priority (2)

Publications (2)

Family

ID=40071877

Family Applications (1)

Country Status (6)

Families Citing this family (12)

Family Cites Families (31)

• 2007
  • 2007-05-24 US US11/753,552 patent/US20080291023A1/en not_active Abandoned
• 2008
  • 2008-05-02 TW TW097116314A patent/TW200847047A/zh unknown
  • 2008-05-16 WO PCT/US2008/064001 patent/WO2008147740A2/en active Application Filing
  • 2008-05-16 JP JP2010509484A patent/JP5328052B2/ja not_active Expired - Fee Related
  • 2008-05-16 EP EP08769500A patent/EP2171678A4/en not_active Ceased
  • 2008-05-16 CN CN200880016964A patent/CN101681486A/zh active Pending

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events