Computer system and method for asset location and monitoring

Abstract

An electronic inventory database is created for a plurality of assets. Unique identifier information (e.g., a QR code) associated with an asset to be included in an inventory / backend database associated with installation at a particular location is obtained. Metadata associated with the unique identifier is determined, the metadata indicating least undescriptive information associated with the asset. The asset metadata is stored in an inventory database related to an installation location at which the asset is installed. A computer network coupled to each asset is scanned to detect metadata and IP addresses associated with each asset coupled to each installation location such that when the detected metadata matches metadata stored in an inventory database of the asset, the IP addresses are indexed with the metadata and installation locations of the asset in the inventory database.

Description

Technical Field

[0001] The disclosed embodiments generally relate to computer-implemented methods and systems for the location, monitoring, identification, and security of information technology (IT) assets. More specifically, the disclosed embodiments relate to a system for determining the location and identification of equipment in an operational technology (OT) system, and for providing monitoring and security for OT assets. Background Technology

[0002] Inventory control of OT / IT assets in equipment racks typically involves personnel periodically visiting each equipment rack and recording its location and the asset ID of each piece of equipment within the rack. This information may be obtained from someone's memory, handwritten on a clipboard, or in a spreadsheet-type spreadsheet. For example, to uniquely identify equipment serving a specific function among physically similar or identical equipment, data centers often print paper labels with human-readable asset IDs and then affix these labels to servers or equipment. The human-readable paper label becomes the unique identifier for identifying the equipment. This method is error-prone, labor-intensive, and risky for two reasons. First, the labels are prone to falling off and degrade over time. Furthermore, the nature of the human interaction involved in creating, printing, and affixing asset IDs can lead to some degree of naming conflicts, whereby human-readable names can be easily copied, mislabeled, misread, misattached, and / or misidentified. Second, the asset ID label can only identify an equipment when a technician can physically locate it. To locate equipment, it is necessary to track the location of equipment with specific asset ID labels. Typically, data centers use some form of inventory record and strive to keep these records up-to-date. However, tracking and maintaining a current inventory record of continuously added, moved, and / or replaced equipment is extremely labor-intensive and error-prone. There is often a serious risk that a technician might operate, reconfigure, move, or replace the wrong piece of equipment, causing significant additional problems.

[0003] This is common practice in current information technology (IT) systems, and creating and maintaining an accurate asset inventory in operational technology (OT) systems requires almost no effort. However, in today's environment with a high focus on cybersecurity, this has become a pressing need and priority for facility managers and process owners. Nevertheless, the ability to create and maintain an accurate asset inventory, and to know the location of each asset, remains unavailable to many OT system owners. Once the asset inventory is established, there is an urgent need to automate its use (extract value). Summary of the Invention

[0004] The objects and advantages of the exemplary embodiments described below will be set forth in and become apparent from the following description. Additional advantages of the illustrated embodiments will be realized and obtained through the written description and its claims, as well as the devices, systems, and methods particularly pointed out in the drawings.

[0005] To achieve these and other advantages, and in accordance with the purposes of the illustrated embodiments, in one aspect, the disclosed embodiments relate to combining debugging and firmware update tools to utilize tags (e.g., QR codes) for creating and maintaining a hierarchical set of information about assets and their associated locations in an asset inventory database.

[0006] In a further aspect, a computer system and method for creating an electronic inventory database for multiple assets are described, wherein what is obtained by the computer device is a unique identifier associated with an asset to be included in the inventory database, the unique identifier being associated with an installation at a location (installation location) on a computer network connected to other installation locations. In some embodiments, the unique identifier is a Quick Response (QR) code generated by a computer device connected to a printing device. The computer device then determines metadata associated with the unique identifier, the metadata indicating the least descriptive information associated with the asset. What is stored by the computer device is the asset metadata in the inventory database associated with the installation location, wherein the asset is operatively connected to the computer network. In some embodiments, the computer device preferably scans the QR code / unique identifier to enable the generation of the inventory / back-end database. The computer device then preferably scans the computer network to detect metadata (e.g., one or more: serial number; device name; device type; model; and IP address associated with each asset connected to each installation location), whereby when the detected metadata matches the metadata stored in the asset's inventory database, the IP address is indexed in the inventory database along with the asset's metadata and installation location. Attached Figure Description

[0007] Therefore, those skilled in the art to which this subject matter pertains will readily understand how to manufacture and use the devices and methods disclosed herein without excessive experimentation. Preferred illustrative embodiments will now be described in detail with reference to certain accompanying drawings, in which:

[0008] Figure 1 An example communication network used in conjunction with one or more of the illustrated embodiments is shown;

[0009] Figure 2 An example network device / node is shown for use with one or more of the illustrated embodiments;

[0010] Figure 3 It is a network diagram indicating the physical locations and related assets according to the illustrated embodiment; and

[0011] Figure 4 This is a flowchart illustrating an exemplary computer-implemented method according to the illustrated embodiment for creating and maintaining an asset inventory database containing a hierarchical set of information associated with assets. Detailed Implementation

[0012] The illustrated embodiments will now be described more fully with reference to the accompanying drawings, wherein like reference numerals denote similar structural / functional features. The illustrated embodiments are not intended to be limited in any way to what is shown, as the illustrated embodiments described below are merely exemplary and, as will be understood by those skilled in the art, can be implemented in various forms. Therefore, it should be understood that any structural and functional details disclosed herein should not be construed as limiting, but merely as the basis for the claims and as an indication to teach those skilled in the art to use the discussed embodiments in various ways. Furthermore, the terminology and phrases used herein are not intended to be limiting, but rather to provide an understandable description of the illustrated embodiments.

[0013] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains. Although any methods and materials similar to or equivalent to those described herein may also be used in the practice or testing of the illustrated embodiments, exemplary methods and materials are described hereafter.

[0014] It is important to note that, as used herein and in the appended claims, the singular forms “a,” “an,” and “the” include plural indicators unless the context clearly specifies otherwise. Thus, for example, a reference to “stimulus” includes a plurality of such stimuli, a reference to “signal” includes a reference to one or more signals and their equivalents known to those skilled in the art, and so on.

[0015] It should be understood that the illustrated embodiments discussed below are preferably software algorithms, programs, or code residing on a computer-usable medium, having control logic for enabling execution on a machine having a computer processor. This machine typically includes memory configured to provide execution output of the computer algorithm or program according to the illustrated embodiments.

[0016] As used herein, the term "software" means synonymous with any code or program that can be implemented in the processor of a host computer, whether its implementation is in hardware, firmware, or as a software computer product available on a disk, memory storage device, or for download from a remote machine. The embodiments described herein include software that implements the above equations, relations, and algorithms. Based on the above embodiments, those skilled in the art will understand further features and advantages of the illustrated embodiments. Therefore, the illustrated embodiments are not limited to what has been specifically shown and described, except as pointed out in the appended claims.

[0017] Now we turn descriptively to the accompanying drawings, in which similar reference numerals in several views denote similar elements. Figure 1 An exemplary communication network 100 is depicted, in which the embodiments shown below can be implemented. It should be understood that the communication network 100 is a collection of geographically distributed nodes interconnected by communication links and network segments for transmitting data between end nodes, such as personal computers, workstations, smartphones, tablets, televisions, sensors, and / or other devices, such as automobiles. Many types of networks are available, ranging from Local Area Networks (LANs) to Wide Area Networks (WANs). LANs typically connect nodes via dedicated private communication links located in the same physical location (such as a building or campus). WANs, on the other hand, typically connect geographically dispersed nodes via long-distance communication links, such as public carrier telephone lines, optical paths, Synchronous Optical Networks (SONETs), Synchronous Digital Hierarchy (SDH) links, or Power Line Communication (PLC), etc.

[0018] Figure 1 This is a schematic block diagram of an exemplary communication network 100, which includes nodes / devices 101-108 interconnected via various communication methods (e.g., sensors 102, client computing devices 103 (e.g., asset inventory creation / maintenance devices), smartphone devices 105, web servers 106, routers 107, switches 108, databases, etc.). For example, link 109 may be a wired link or may include a wireless communication medium, wherein some nodes communicate with other nodes based on factors such as distance, signal strength, current operating status, location, etc. Furthermore, as those skilled in the art will understand, where appropriate, each device may use predefined network communication protocols, such as various wired and wireless protocols, to communicate data packets (or frames) 142 with other devices. In this case, the protocol consists of a set of rules defining how nodes interact with each other. Those skilled in the art will understand that any number of nodes, devices, links, etc., can be used in a computer network, and the views shown herein are for simplicity. Furthermore, although embodiments are shown herein with reference to a general network cloud, the description herein is not limited thereto and can be applied to hardwired networks.

[0019] As those skilled in the art will understand, aspects of the illustrated embodiments may be embodied as a system, method, or computer program product. Therefore, aspects of the illustrated embodiments may take the form of a completely hardware embodiment, a completely software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining software and hardware aspects, which are generally referred to herein as “device,” “apparatus,” “module,” or “system.” Furthermore, aspects of the illustrated embodiments may take the form of a computer program product contained in one or more computer-readable media, on which computer-readable program code is included.

[0020] Any combination of one or more computer-readable media may be used. A computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. A computer-readable storage medium can be, for example, but not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof. More specific examples (not an exhaustive list) of computer-readable storage media will include: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In the context of this document, a computer-readable storage medium can be any tangible medium capable of containing or storing a program used by or in connection with an instruction execution system, apparatus, or device. A computer-readable signal medium may include a propagated data signal containing computer-readable program code, for example, in baseband or as part of a carrier wave. Such a propagated signal can take any of a variety of forms, including but not limited to electromagnetic, optical, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium that is not a computer-readable storage medium and can transmit, propagate or transfer a program used by or in connection with an instruction execution system, apparatus or device.

[0021] The program code contained on a computer-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, fiber optic cable, RF, etc., or any suitable combination thereof. The computer program code for performing the operations of various aspects of this invention may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, Smalltalk, C++, Python, etc., and conventional procedural programming languages ​​such as the "C" programming language or similar programming languages. The program code may be executed entirely on the user's computer as a standalone software package, partially on the user's computer, partially on the user's computer, partially on a remote computer, or entirely on a remote computer or server. In the latter case, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet through an Internet service provider).

[0022] The aspects of the illustrated embodiments are described below with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to the illustrated embodiments. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a computer device, a special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams.

[0023] These computer program instructions may also be stored in a computer-readable medium that can instruct a computer, other programmable data processing device, or other equipment to operate in a particular manner, such that the instructions stored in the computer-readable medium generate and maintain an inventory asset database, which includes instructions that implement functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0024] Computer program instructions may also be loaded onto a computer, other programmable data processing apparatus or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device, thereby producing a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide a process for implementing the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0025] Figure 2This is a schematic block diagram of an example network computing device 200 (e.g., asset inventory creation / maintenance device 103, server / back-end database 106, etc.) that can be used (or components thereof) with one or more embodiments described herein (e.g., as one of the nodes shown in network 100) to provide a computer-implemented process for creating and maintaining an asset inventory database containing a hierarchical set of location information associated with assets. As mentioned above, in different embodiments, these different devices are configured to communicate with each other in any suitable manner, such as via communication network 100.

[0026] Device 200 is intended to represent any type of computer system capable of performing the teachings of the various embodiments shown. Device 200 is merely one example of a suitable system and is not intended to impose any limitation on the scope of use or functionality of the embodiments shown herein. In any case, computing device 200 is capable of implementing and / or performing any of the functions set forth herein, particularly for creating and maintaining an asset inventory database containing a hierarchical set of information associated with assets, and more preferably providing secure software updates for inventory assets.

[0027] It should be understood and appreciated that computing device 200 can operate in many other general-purpose or special-purpose computing system environments or configurations. Examples of well-known computing systems, environments, and / or configurations suitable for computing device 200 include, but are not limited to, personal computer systems, server computer systems, thin clients, fat clients, handheld or laptop devices, multiprocessor systems, microprocessor-based systems, network PCs, minicomputer systems, and distributed data processing environments that include any of the aforementioned systems or devices. Computing device 200 can be described in the general context of computer system executable instructions, such as program modules, executed by a computer system. Typically, program modules can include routines, programs, objects, components, logic, data structures, etc., that perform a specific task or implement a specific abstract data type. Computing device 200 can be implemented in a distributed data processing environment where tasks are performed by remote processing devices linked via communication network 100. In a distributed data processing environment, program modules can reside in local and remote computer system storage media, including memory storage devices.

[0028] Components of device 200 may include, but are not limited to, one or more processors or processing units 216, system memory 228, and a bus 218 that connects various system components, including system memory 228, to processor 216. Bus 218 represents one or more of several types of bus architectures, including memory buses or memory controllers, peripheral buses, accelerated graphics ports, and processor or local buses using any of a variety of bus architectures. By way of example and not limitation, such architectures include Industry Standard Architecture (ISA) buses, Micro Channel Architecture (MCA) buses, Enhanced ISA (EISA) buses, Video Electronics Standards Association (VESA) local buses, and Peripheral Component Interconnect (PCI) buses. Computing device 200 typically includes various computer system readable media. This media can be any available media accessible to device 200, and it includes volatile and non-volatile media, removable and non-removable media.

[0029] System memory 228 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 230 and / or cache memory 232. Computing device 200 may also include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, storage system 234 may be provided for reading from and writing to a non-removable, non-volatile magnetic medium (not shown, and generally referred to as a "hard disk drive"). Although not shown, a disk drive for reading from and writing to a removable, non-volatile disk and an optical disk drive for reading from or writing to a removable, non-volatile optical disk, such as a CD-ROM, DVD-ROM, or other optical media, may be provided. In this case, each may be connected to bus 218 via one or more data media interfaces. As will be further described and illustrated below, memory 228 may include at least one program product having a set (e.g., at least one) of program modules 240 configured to perform the functions of embodiments of the illustrated embodiments, such as creating and maintaining an asset inventory database containing a hierarchical set of information associated with assets, and preferably further providing security software updates for the inventoried assets.

[0030] By way of example and not limitation, a program / utility 240 having a set (at least one) of program modules 215 (e.g., an asset inventory module), along with an operating system, one or more applications, other program modules, and program data, may be stored in memory 228. Each of the operating system, one or more applications, other program modules, and program data, or some combination thereof, may include an implementation of a network environment. Program modules 215 typically perform the functions and / or methods of the embodiments described herein.

[0031] Device 200 can also communicate with one or more external devices 214, such as a keyboard, pointing device, display 224, etc.; one or more devices that enable a user to interact with computing device 200; and / or any device (e.g., network interface card, modem, etc.) that enables computing device 200 to communicate with one or more other computing devices. This communication can be performed via input / output (I / O) interface 222. Furthermore, device 200 can communicate with one or more networks, such as a local area network (LAN), a general wide area network (WAN), and / or a public network (e.g., the Internet), via network adapter 220. As shown, network adapter 220 communicates with other components of computing device 200 via bus 218. It should be understood that, although not shown, other hardware and / or software components can be used in conjunction with device 200. Examples include, but are not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archiving storage systems.

[0032] Figure 1 and Figure 2 The following brief general description is intended to provide an illustrative and / or suitable exemplary environment in which the embodiments described below can be implemented. Figure 1 and 2 This is an example of a suitable environment and is not intended to impose any limitation on the structure, scope of use, or functionality of the illustrated embodiments. A particular environment should not be construed as having any dependency or requirement on any component or combination thereof shown in the exemplary operating environment. For example, in some cases, one or more elements of the environment may be considered unnecessary and omitted. In other cases, one or more additional elements may be considered necessary and added.

[0033] With the exemplary communication network 100 ( Figure 1 ) and computing devices 200 ( Figure 2 The embodiments shown and discussed above are generally illustrated; a description of some of the illustrated embodiments will now be provided. It should be understood and appreciated that, in implementing… Figure 1-4 Exemplary embodiments of one or more components relate to an asset inventory database for creating and maintaining a hierarchical set of information (including physical location information) associated with an asset (e.g., a circuit breaker component), and preferably to providing secure software updates for the inventory assets.

[0034] According to the illustrated embodiment, a unique tag is created and provided to each operational technology (OT) asset (e.g., Figure 3(Ref. 302-312). An example of an OT asset could be a circuit breaker assembly; however, the disclosed embodiments should not be construed as limited to use with such OT circuit breaker assets, as the disclosed embodiments are applicable to any OT asset that will be cataloged in an inventory asset database and is preferably associated with a physical location (preferably with an associated IP address). Furthermore, according to the disclosed illustrated embodiments, a unique tag to be associated with the OT asset and its physical location is placed (e.g., within a component cabinet, room, building, etc.) and will be described below as a Quick Response (QR) code / tag. However, it should be recognized and understood that the disclosed illustrated embodiments should not be construed as limited to such QR code tags, as the illustrated embodiments will include other tags, preferably with printed markings indicating metadata describing the equipment (e.g., circuit breaker assembly) and / or location (e.g., component cabinet and its physical location) to which it is attached / associated.

[0035] According to the illustrated embodiment, a hierarchical set of unique QR codes is created for each physical location (e.g., 314-330) where the OT asset (302-312) resides. For example, this might include locations within each of the aforementioned locations, starting from a room (e.g., 314), then mounting structures (switchboards, distribution panels, racks, etc.) (e.g., 316, 318), then mounting structures (batteries, cabinets, slots, etc.) (e.g., 302-312). In some embodiments, the QR codes are generated by a computer device 103 connected to a printing device for printing QR codes. For example, in addition to general device metadata such as model number and serial number, QR codes can be generated "on demand" when the physical device location and network address are known (as further described herein).

[0036] According to the illustrated embodiment, scanning the QR code (e.g., via an optical scanning device operatively coupled to computer device 103) provides a digital fingerprint, which is unique for each print of the same QR code to be identified and associated with, and is recorded in a back-end database system (e.g., 106). Furthermore, according to the illustrated embodiment, when scanning the QR code during a firmware upgrade process (e.g., via computer device 103), preferably for OT assets (302-312), its fingerprint is determined and checked against fingerprints on documents in the inventory database (e.g., 106) to authenticate the QR code as genuine. This thus provides anti-counterfeiting protection for the QR code associated with the OT asset and its physical location.

[0037] Preferably, the physical installation structure (e.g., 316-330) of the assets (e.g., 302-312) is already affixed with QR codes upon shipment. Additional QR codes (including printed / generated QR code labels) can be provided for rooms (e.g., 314) and to meet other needs (e.g., adding new / replacing OT assets). During the commissioning of the OT assets (e.g., 302-312), each physical location QR code (e.g., 302-330) is scanned by computer device 103, and its name and descriptive physical location information, as well as the QR code of the physical element to which it belongs, are preferably determined by computer 103 and entered into database 106. Then, preferably, the QR code, location information (e.g., cabinet 2C, 320), and the QR codes of its next-level elements (e.g., switchgear series 1, 316) are recorded in the back-end database 106. It should be understood that this constructs a hierarchical structure of physical locations in database 106. Alternatively, prior to arrival at the site, information from the electrical single-line diagram and QR codes printed by the equipment / asset supplier / manufacturer are entered into computer device 103, and then the QR codes are placed in their appropriate locations during on-site OT asset commissioning. In some embodiments, and as further described herein, a mobile application or software on portable computer device 103 (e.g., a laptop computer) is used to scan the QR codes in order to create / generate an initial backend database 106.

[0038] According to the illustrated embodiment, during the trial operation of the OT asset (e.g., 302-312), its QR code and the QR codes of the final components (e.g., units 4A, 330) installed therein are scanned by computer device 103 and recorded in backend database 106. Preferably, the information retrieved by computer device 103 when scanning the OT asset includes the serial number and other device-specific information about the OT asset, such as the device type (where applicable), and may also include the firmware version of the OT asset provided by the factory / manufacturer / supplier.

[0039] Preferably, once the tool / inventory computer device 103 has scanned the OT asset QR codes of all devices, the tool / inventory computer device 103 scans the OT assets (e.g., 302-312) preferably to which they are typically connected (e.g., network 100) to retrieve the serial number and IP address associated with each OT asset, so as to match the serial number of the scanned OT asset with serial numbers stored in a back-end database (e.g., 106), such that when a matching serial number is determined, the aforementioned associated IP address is also stored in the catalog database in association with its serial number. Any IP address that does not match an entry in the back-end asset inventory database is marked and highlighted to draw further attention.

[0040] Furthermore, according to some embodiments, when firmware updates and / or patches need to be installed on certain OT assets (e.g., 302-312), the tool / inventory computer device 103 captures device information of the OT asset via a communication network (e.g., 100) to verify the information against information retrieved from the device's QR code stored in the backend database 106, ensuring a match. If the information stored in the backend database 106 and the information retrieved from the OT asset are inconsistent, an alert is preferably issued. And if verified (information matches), preferably, the firmware update tool provided in the tool / inventory computer device 103 continues to upload new firmware to the OT asset device and update the device information in the backend database 106 (using the information retrieved from the OT asset device), preferably using the firmware version to which the device has been updated. Preferably, communication with the backend asset inventory database 106 is conducted via a Transport Layer Security (TLS) connection.

[0041] Based on the brief description of certain illustrative embodiments provided above, reference is now made to... Figure 3 and Figure 4 (and continue to refer to) Figure 1 and Figure 2 The process 400 for creating and maintaining an asset inventory database 106 containing a hierarchical set of information associated with assets, according to an illustrative embodiment, will now be described. It should be understood and appreciated that... Figure 1-4 This is an example of a suitable environment and is not intended to impose any limitation on the structure, scope of use, or functionality of the illustrated embodiments. A particular environment should not be construed as having any dependency or requirement on any component or combination thereof shown in the exemplary operating environment. For example, in some cases, one or more elements of the environment may be considered unnecessary and omitted. In other cases, one or more additional elements may be considered necessary and added.

[0042] Now for reference Figure 4Process 400, now described according to an illustrative embodiment, is a computer-implemented method for creating and maintaining an asset inventory database containing a hierarchical set of information associated with assets. Beginning at step 402, an inventory database (106) (described further below) is preferably generated by computer device 103. This database 106 preferably contains a structured inventory database comprising multiple physical locations (314-318 and 320-330), wherein an asset (e.g., 302) and the installation location (e.g., 320) to which the asset is to be associated are, at least in step 404, the computer device 103 preferably scans a Quick Response (QR) code associated with the installation location (e.g., 320) to which the asset (e.g., 302) is to be associated. Each installation location (314-318 and 320-330) and asset (e.g., 302-312) are preferably communicatively connected to a public computer network (e.g., 100). The scanned QR code provides metadata (e.g., location metadata) indicating the installation location (e.g., 320) and each physical location (e.g., 314, 316) hierarchically associated with the installation location (e.g., 320).

[0043] Next, in step 406, computer device 103 preferably scans the QR code associated with the asset (e.g., 302) to be included in inventory database 106. Then, in step 408, computer device 103 preferably determines the metadata (asset metadata) associated with the scanned asset QR code (step 406), which indicates minimal descriptive information associated with the asset (e.g., but not limited to: serial number; device name; device type; model; and firmware information associated with the associated asset (e.g., 302)). Next, in step 410, computer device 103 stores the aforementioned determined asset and location metadata in inventory database 106, such that they are associated / related to each other.

[0044] In step 412, a computer device 103, operatively connected to the database 106 and communication network 100 shared by each asset (e.g., 302-312) and physical locations (314-318 and 320-330), preferably scans the computer network 100 to detect at least asset metadata and the IP address associated with each asset (e.g., 302-312). The computer device 103 is then operatively capable of determining when the scanned asset metadata matches the asset metadata stored in the inventory database of the asset (e.g., 302) (step 410). When a match is determined, the detected IP address of the asset (e.g., 302) is then indexed in the inventory database 106 to also relate / associate with the asset and location metadata of the asset (e.g., 302) previously stored in the inventory database 106 (step 310).

[0045] In some illustrated embodiments, in step 414, computer device 103 is further operable and configured to determine the availability of software / firmware updates for each asset (e.g., 302-312) in inventory database 106 by detecting the availability of software and / or firmware updates, preferably from one or more databases, preferably external to the inventory database, associated with each asset (e.g., 302-312) stored in asset inventory database 106. For example, when a software / firmware version of an asset (e.g., 302) is stored in inventory database 106, and computer device 103 determines that an update to the software / firmware version available for that asset (e.g., 302) is available, preferably a software update tool / module associated with computer device 103 is provided and / or configured and operated to update the asset (e.g., 302) with the detected new software / firmware version. Alternatively, computer device 103 sends a message / notification (preferably via a known suitable communication channel (e.g., email, txt, computer text, etc.)) to a network administrator indicating the availability of such an updated software / firmware version for the asset (e.g., 302).

[0046] In some other embodiments shown, computer device 103 is also operated and configured in step 416 to determine the authenticity of the QR code physically associated with the asset (e.g., 302) by comparing asset metadata associated with the QR code physically associated with the asset with asset metadata previously stored (step 410) in the inventory database 106 associated with the asset. For example, if no match is determined, this could indicate that the asset device (e.g., 302) may have been tampered with (e.g., exchanged with a counterfeit device) because its physically associated QR code does not match a previously associated QR code (e.g., at the time of its installation) previously stored (step 410) in the inventory database 106.

[0047] In another illustrative embodiment, computer device 103 is configured and operated to generate a computer network diagram (e.g., as shown in the diagram) indicating hierarchically associated physical locations (e.g., 314-318 and 320-330) and assets included in the hierarchically associated physical locations (e.g., 302-312). Figure 3 (As shown). For example, the generated computer network diagram may include a graphical representation associated with each corresponding physical location and asset identified in the computer network diagram.

[0048] Regarding the illustrative embodiments described above, it should be understood that the various non-limiting embodiments described herein can be used alone, in combination, or selectively combined for a particular application. Furthermore, some features of the various non-limiting embodiments described above may be used without corresponding use of the other described features. Therefore, the foregoing description should be considered merely as an illustration of the principles, teachings, and exemplary embodiments of the invention, and not as a limitation thereof.

[0049] It should be understood that the above arrangements are merely illustrative of the application of the principles of the illustrated embodiments. Many modifications and alternative arrangements can be devised by those skilled in the art without departing from the scope of the illustrated embodiments, and the appended claims are intended to cover such modifications and arrangements.

Claims

1. A computer-implemented method for creating an electronic inventory database for multiple assets, comprising: A unique identifier is obtained by computer equipment and associated with at least a first asset among a plurality of assets to be included in an inventory database. The first asset is associated with an installation at a location (installation location), wherein a computer network is typically associated with the installation location, other installation locations, and the computer equipment. The computer device determines metadata associated with the unique identifier, the metadata indicating descriptive information (asset metadata) associated with the first asset; In connection with the installation location operatively associated with the first asset, the computer device stores the asset metadata in an inventory database; The computer device scans the computer network to detect metadata and IP addresses associated with the first asset on the computer network. Whereby, when the detected metadata matches asset metadata for the first asset stored in an inventory database, the detected IP address is indexed in the inventory database by the asset metadata for the first asset and the installation location.

2. The computer-implemented method according to claim 1, wherein the unique identifier is a Quick Response (QR) code.

3. The computer-implemented method according to claim 2, wherein the QR code is generated by a printing device connected to the computer device.

4. The computer-implemented method of claim 2, wherein the inventory database is generated by scanning one or more QR codes by the computer device.

5. The computer-implemented method according to claim 1, wherein the asset metadata includes one or more of the following: serial number; device name; device type; model; MAC address; and firmware information associated with the first asset.

6. The computer-implemented method of claim 1, wherein obtaining a unique identifier associated with a first asset to be included in the inventory database further comprises determining, by the computer device, the installation location where the first asset is to be installed.

7. The computer-implemented method of claim 1, further comprising determining the availability of software updates for the first asset included in the inventory database by the computer device detecting the availability of software and / or firmware updates related to the first asset stored in the inventory database from one or more databases outside the inventory database.

8. The computer-implemented method of claim 2 further includes determining the authenticity of the QR code physically associated with the first asset by comparing metadata associated with the QR code physically associated with the first asset with asset metadata stored in an inventory database associated with the first asset.

9. The computer-implemented method of claim 1, wherein the inventory database is configured to include a plurality of physical locations, wherein the installation location associated with the first asset is hierarchically associated within at least one other physical location, thereby hierarchically associating the computer equipment with the plurality of physical locations hierarchically associated with the first asset.

10. The computer-implemented method of claim 8, further comprising generating a computer network diagram by the computer device, the computer network diagram indicating all hierarchically associated physical locations and each of a plurality of assets included in the hierarchically associated physical locations, and wherein generating the computer network diagram further comprises generating a graphical representation associated with each corresponding physical location and each of the plurality of assets identified in the computer network diagram.

11. A computer-implemented method for creating an electronic inventory database for multiple assets, comprising: An inventory database is generated by computer equipment, and the inventory database is constructed to include multiple hierarchically related physical locations; The computer device scans a Quick Response (QR) code associated with an installation location to be associated with at least a first asset among the plurality of assets, wherein a computer network is typically connected to the first asset, the installation location, and other installation locations, and wherein the scanned QR code provides metadata (location metadata) indicating the installation location and at least one other physical location hierarchically associated with the installation location. The computer device scans the QR code associated with at least a first asset to be included in the inventory database; The computer device determines metadata (asset metadata) associated with the scanned asset QR code, the metadata indicating the least descriptive information associated with the first asset; The computer device stores the asset metadata and the location metadata in association with each other in the inventory database; and The computer device scans the computer network to detect metadata and IP addresses associated with the first asset on the computer network, whereby when the detected metadata matches asset metadata for the first asset stored in the inventory database, the detected IP address is indexed in the inventory database in association with the first asset.

12. The computer-implemented method of claim 11, wherein the asset metadata includes one or more of the following: serial number; device name; device type; model; MAC address; and firmware information associated with the first asset.

13. The computer-implemented method of claim 12, further comprising determining the availability of a software update for each of the plurality of assets in the inventory database by the computer device detecting the availability of software and / or firmware updates associated with each of the plurality of assets stored in the asset database from one or more databases outside the inventory database.

14. The computer-implemented method of claim 12, further comprising the computer device determining the authenticity of the QR code physically associated with at least the first asset by comparing asset metadata associated with the QR code physically associated with the first asset with asset metadata stored in an inventory database associated with the first asset.

15. The computer-implemented method of claim 13, further comprising generating a computer network diagram by the computer device, the computer network diagram indicating all hierarchically associated physical locations and each of a plurality of assets included in the hierarchically associated physical locations.

16. The computer-implemented method of claim 15, wherein generating the computer network graph further comprises generating a graphical representation associated with each corresponding physical location and each of a plurality of assets identified in the computer network graph.

17. A computer device for creating an electronic inventory database for multiple assets, comprising: Memory, configured to store instructions; A processor is arranged to communicate with the memory, wherein the processor is configured to: By scanning a Quick Response (QR) code associated with at least a first asset among a plurality of assets, metadata (asset metadata) associated with the first asset to be included in the inventory database is received, wherein the first asset is associated with an installation at a specific location (installation location), wherein a computer network is typically connected to the installation location, the first asset and other installation locations; The asset metadata is stored in an inventory database associated with the installation location where the asset is operatively connected; and The computer network is scanned to detect metadata and IP addresses associated with the first asset on the computer network, whereby when the detected metadata matches asset metadata for the first asset stored in the inventory database, the detected IP address is indexed in the inventory database by the asset metadata and installation location for the first asset.

18. The computer device of claim 17, wherein the inventory database is configured to include a plurality of physical locations, wherein the installation location associated with the first asset is hierarchically associated within at least one other physical location.

19. The computer device of claim 18, wherein the processor is further configured to determine the physical location associated with each layer of the first asset.

20. The computer device of claim 17, wherein the processor is further configured to: The availability of software updates for each asset included in the inventory database is determined by detecting the availability of software and / or firmware updates related to one or more assets among a plurality of assets stored in the inventory database from one or more databases outside the inventory database; and The authenticity of a QR code physically associated with at least one of the multiple assets is determined by comparing the metadata associated with the QR code physically associated with at least one of the multiple assets with the asset metadata stored in an inventory database associated with at least one of the multiple assets.

Images