System and method for asset mapping interface for information technology infrastructure

Abstract

A method includes performing, by at least one processor, the following: sending a query including an asset identifier; receiving a data structure of the asset, the data structure including a determined relationship between the asset and other hardware and software assets; rendering the data structure into a format capable of being displayed; and displaying the rendered data structure.

Description

[0001] Cross - reference to related patent applications

[0002] This application claims the priority benefit of U.S. Application No. 18 / 053,804, filed on November 9, 2022, which claims the priority benefit of Indian Application No. 202211051334, filed on September 8, 2022; the U.S. Application No. 18 / 053,804 and the Indian Application No. 202211051334 are hereby incorporated by reference in their entirety and made a part of this invention. Technical Field

[0003] Various embodiments of the present disclosure generally relate to an interface for an automated framework for correlating infrastructure components. Background Art

[0004] Network information technology infrastructure can include a large number of assets. Assets can refer to hardware products or components, or can also refer to software programs or configurations. Currently available products do not provide the centralized asset management and mapping tools required for global infrastructure operations, which can provide a robust interface for the health and readiness of assets, the relationships between assets, asset problem tracking, asset events, and configuration change history. Therefore, asset and operations management still face difficulties. Currently available products do not provide a lookup table or reference diagram, and when an asset has a problem, it is impossible to find the impact or "blast radius" of the configuration item. The "blast radius" used in the present invention can refer to a measure of the overall impact of potential problems of an asset. The present disclosure aims to overcome one or more of the above limitations of the hitherto known technologies. Summary of the Invention

[0005] In some aspects, the technology described in the present invention relates to a method, including: performing the following operations by at least one processor: sending a query including an asset identifier; receiving a data structure of the asset, wherein the data structure includes the determined relationships between the asset and other hardware and software assets; rendering the data structure into a format for display; and displaying the rendered data structure.

[0006] In some aspects, the technology described in the present invention relates to a method, wherein a link algorithm is applied to the standardized data copied from the response file generated by the asset in response to an instruction sent to the asset, the data structure is created based on the link algorithm, and the standardized data copied from the response file is verified based on the logging events associated with the copying of the standardized data from the response file.

[0007] In some aspects, the technology described in the present invention relates to a method, wherein the sending of the query includes sending a query to an external application.

[0008] In some aspects, the technology described in the present invention relates to a method, wherein the assets include one or more of storage assets, computer assets, operating system assets, database assets, or application program assets.

[0009] In some aspects, the technology described in the present invention relates to a method, wherein the determining relationships include one or more of a storage asset linked to a computer asset by a volume unique identifier, a computer asset linked to an operating system asset by a guest identifier, an operating system asset linked to a database asset by a guest name, or a database asset linked to an application program asset by a database name.

[0010] In some aspects, the technology described in the present invention relates to a method, wherein data from a response file is verified by prompting approval team members to verify data changes.

[0011] In some aspects, the technology described in the present invention relates to a method, wherein the displaying the rendered data structure includes associating display colors with assets based on information in a ticketing tool.

[0012] In some aspects, the technology described in the present invention relates to a method, wherein the response file includes one or more of volume characteristics of a storage asset, virtual machine information of a computer asset, virtual disk information of a computer asset, physical storage information of a computer asset, guest server information of a database asset, database size information of a database asset, database name information of a database asset, or database disk associations of a database asset.

[0013] In some aspects, the technology described in the present invention relates to a method, wherein the displaying the rendered data structure includes determining support members of the assets and displaying the determined support members.

[0014] In some aspects, the technology described in the present invention relates to a method, wherein the sending the query includes sending a query via a Uniform Resource Locator; and wherein the receiving the data structure includes receiving a data structure from an external application via JavaScript Object Notation.

[0015] In some aspects, the technology described in the present invention relates to a system, including: a memory that can store instructions; at least one processor for executing the stored instructions to perform a method including the following steps: sending a query including an asset identifier; receiving a data structure of the asset, wherein the data structure includes determined relationships between the asset and other hardware and software assets; rendering the data structure into a format for display; and displaying the rendered data structure.

[0016] In some aspects, the technology described in the present invention relates to a system, in which a linking algorithm is applied to standardized data copied from a response file generated by an asset in response to an instruction sent to the asset, and the data structure is created based on the linking algorithm, wherein the standardized data copied from the response file is verified based on a logging event associated with copying the standardized data from the response file.

[0017] In some aspects, the technology described in the present invention relates to a system, in which the sending of the query includes sending a query to an external application.

[0018] In some aspects, the technology described in the present invention relates to a system, in which the asset includes one or more of a storage asset, a computer asset, an operating system asset, a database asset, or an application asset.

[0019] In some aspects, the technology described in the present invention relates to a system, in which the determining of the relationship includes one or more of a storage asset linked to a computer asset by a volume unique identifier, a computer asset linked to an operating system asset by a guest identifier, an operating system asset linked to a database asset by a guest name, or a database asset linked to an application asset by a database name.

[0020] In some aspects, the technology described in the present invention relates to a system, in which the data from the response file is verified by prompting approval team members to verify data changes.

[0021] In some aspects, the technology described in the present invention relates to a system, in which the displaying of the rendered data structure includes associating a display color with an asset based on information in a ticketing tool.

[0022] In some aspects, the technology described in the present invention relates to a system, in which the response file includes one or more of volume characteristics of a storage asset, virtual machine information of a computer asset, virtual disk information of a computer asset, physical storage information of a computer asset, guest server information of a database asset, database size information of a database asset, database name information of a database asset, or database disk association of a database asset.

[0023] In some aspects, the technology described in the present invention relates to a system, in which the displaying of the rendered data structure includes determining support members of the asset and displaying the determined support members.

[0024] In some aspects, the technology described in the present invention relates to a non-transitory computer-readable medium storing instructions which, when executed by at least one processor, cause the at least one processor to perform a method comprising the steps of: sending a query including an asset identifier; receiving a data structure of the asset, wherein the data structure includes determined relationships between the asset and other hardware and software assets; rendering the data structure into a format for display; and displaying the rendered data structure.

[0025] More purposes and advantages of the disclosed embodiments will be partially described in the following description and partially understood, or can be learned through the practice of the disclosed embodiments. These purposes and advantages of the disclosed embodiments can be achieved and obtained by using the elements and combinations specifically pointed out in the appended claims.

[0026] It should be understood that the above general description and the following specific embodiments are only for exemplary and illustrative purposes, rather than limiting the disclosed embodiments claimed. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] The drawings included in and forming a part of this specification illustrate various exemplary embodiments and, together with the following description, illustrate the principles of the disclosed embodiments.

[0028] Figure 1 Shows an example system block diagram mapping relationships between assets in a network information technology infrastructure according to one or more embodiments.

[0029] Figure 2 Shows an example asset link diagram according to one or more embodiments.

[0030] Figure 3 Shows an example storage inventory user interface according to one or more embodiments.

[0031] Figure 4 Shows another example user interface according to one or more embodiments.

[0032] Figure 5 Is a flowchart showing an example process logic flow for providing an interface for mapping relationships between assets in a network information technology infrastructure according to one or more embodiments.

[0033] Figure 6 Shows an implementation of a general computer system that can execute the technology described in the present invention according to one or more embodiments.

[0034] Figure 7 Shows an example table of a user interface according to one or more embodiments.

[0035] Figure 8Displays another example table of a user interface according to one or more embodiments.

[0036] Figure 9 Displays another example user interface according to one or more embodiments. Detailed Description

[0037] The following embodiments introduce an interface for an automation framework for associating infrastructure components, and more specifically, a system and method for an interface for mapping relationships between hardware and software assets in a network information technology infrastructure.

[0038] A network information technology infrastructure can include a large number of assets. Assets can refer to hardware products or components, or can also refer to software programs or configurations. Currently available products do not provide centralized asset management and mapping tools required for global infrastructure operations, and global infrastructure operations can provide a robust interface for the health and readiness of assets, the relationships between assets, asset issue tracking, asset events, and configuration change history. Therefore, asset and operations management still faces difficulties. Currently available products do not provide a lookup table or reference diagram, and when an asset has a problem, the blast radius of the configuration item cannot be found. Similarly, the blast radius can refer to a way to measure the overall impact of potential problems of an asset.

[0039] Creating a fully functional configuration management database is a challenge for many companies, and enterprises usually make significant investments in underlying infrastructure, professional services, and licenses. These projects are long-term and rarely meet all the needs of enterprises. Enterprises may encounter complex tables that are difficult to maintain and browse.

[0040] In addition, when application teams discover problems, they may use different infrastructure management teams to investigate the problems. Some information from one team may depend on the investigation results of another team. This information dependence often leads to problems not being resolved in a timely manner. At the same time, incorrect configuration items may also be identified, which hinders efficient investigation and often leads to an overall delay in problem solving.

[0041] In addition, since information from different data sources may be raw information, information from different data sources (such as information from databases or storage networks) may be sent to a centralized repository for artificial intelligence and / or machine learning algorithms. Therefore, for a large amount of information, processing data in a centralized repository may become complex, and the management of the centralized repository may become unsustainable and costly.

[0042] This disclosure aims to overcome one or more of the above challenges.

[0043] The principles of the present disclosure are illustrated by reference to illustrative embodiments of specific applications, but it should be understood that the present disclosure is not limited to these embodiments. Those of ordinary skill in the art and those guided by the present invention will recognize that other modifications, applications, embodiments, and substitutions of equivalent solutions are within the scope of the embodiments described by the present invention. Therefore, it should be considered that the present disclosure is not limited by the above description.

[0044] The various non-limiting embodiments of the present disclosure will now be described to provide an overall understanding of the structure, function, and principle of use of the systems and methods disclosed in the present invention.

[0045] Selected examples disclosed and described in detail with reference to the accompanying drawings illustrate one or more examples of these non-limiting embodiments. Those of ordinary skill in the art will understand that the systems and methods specifically described and shown in the drawings are non-limiting embodiments. Features shown or described in connection with one non-limiting embodiment may be combined with features of other non-limiting embodiments. Such modifications and variations are within the scope of the present disclosure.

[0046] The following embodiments introduce an interface for an asset and / or inventory information storage framework that can store multi-vendor product information purchased by a company.

[0047] The following embodiments may include an interface for interacting with information captured by a data collection agent that can capture information related to the sub-converged infrastructure generated by assets. Such information for computer assets may include virtual servers, storage, networks, CPUs, and memories. Such information for database assets may include database names, storage, and the servers where they are located. Such information for storage assets may include created volumes, storage pools, server mappings, and shares.

[0048] Assets can be linked to other assets through various data. For example, a storage asset can be linked to a computer asset through a volume unique identifier. A computer asset can be linked to an operating system asset through a guest identifier. An operating system asset can be linked to a database asset through a guest name. A database asset can be linked to an application asset through a database name.

[0049] The following embodiments may include an interface for interacting with information provided by an association engine that is used to map and transform asset information into standard tags for importing data from two different data sources. For example, a unique volume identifier can be used to link computer and storage assets. A database asset can be a structure with various database platforms on various network-attached storage assets. The assets can be linked in the sub-converged infrastructure and populated into a configuration management database.

[0050] The following embodiments may include an interface for interacting with information provided by a component that transforms a configuration management database (including a converged infrastructure with linked assets) into a searchable web application. The web application may provide an interface for displaying and searching a converged infrastructure with linked assets.

[0051] Figure 1 Shows an example system block diagram for mapping relationships between assets in a network information technology infrastructure according to one or more embodiments.

[0052] A system 100 for mapping relationships between assets in a network information technology infrastructure may include various components, including an inventory source and data collection 101, business logic 102, asset relationship links 103, and an application programming interface 104. The inventory source and data collection 101 may include hardware and software assets and raw data collected from the assets. The business logic 102 may include connections between assets, virtual schemas, asset mapping rules, and domain knowledge. The asset relationship links 103 may include assets, boundaries, and a converged infrastructure provided for linking the assets together. The application programming interface (API) 104 may include various tools for retrieving and displaying information related to assets and relationships.

[0053] A system 100 for mapping relationships between assets in a network information technology infrastructure may include various components. For example, the system 100 may include database servers 111, 112, and 113 connected to an API gateway 141. The system 100 may include computers 121, 122, and 123 connected to an API gateway 142. The system 100 may include storages 131, 132, and 133 connected to an API gateway 143. The database servers 111, 112, 113, the computers 121, 122, 123, the storages 131, 132, and 133 may be example assets of a network information technology infrastructure.

[0054] API gateways 141, 142, and 143 can be connected to a data collection script (DCS) 151. The DCS 151 can collect data from one or more of database servers 111, 112, 113, computers 121, 122, 123, storages 131, 132, or 133 through API gateway 141, API gateway 142, or API gateway 143. The DCS 151 can be connected to business logic 152. The business logic 152 can be connected to database 153. The database 153 can be connected to network node 154. The network node 154 can be connected to HTTP node 171. The HTTP node 171 can be connected to database 153 and business logic 172. The business logic 172 can be connected to configuration change server 173. The configuration change server 173 can be connected to API gateways 141, 142, and 143. User 161 can access system 100 through device 162 via validator 163 and web application 164. The web application 164 can be connected to network node 154.

[0055] The web application 164 can include features such as a watchtower, a guard sentinel, a helper tool, and mecha. The "watchtower" can provide a customized web application for reporting for a specific technology. The "guard sentinel" can provide the ability to send customized reports and customized alerts for specific issues via email. The helper tool can support contracts, data center locations, downstream message routers, racks, access routes, standard operating procedures (SOPs), etc. Mecha can provide automated robots or programs for "business as usual (BAU)" operations such as self-healing and auto-configuration.

[0056] System 100 can use application programming interface (API) calls on assets to retrieve asset format data and convert the retrieved asset format data into standard format data. The standard format data can be displayed on a user interface such as the web application 164, thus providing an overview of multiple assets. In addition, user 161 can change the asset configuration from the web application 164 through the configuration change server 173.

[0057] For example, the instructions of the DCS 151 can be implemented using PowerShell and / or Python. For example, the instructions of the business logics 152 and 172 can be implemented in open source code including PapaParse, C3.js, and / or jQuery. For example, the instructions of the web application 164 can be implemented using HTML, CSS, JavaScript, and / or NODE.js. However, the above examples are for illustrative purposes only, and the present disclosure is not limited to the above embodiments.

[0058] For example, the business logic 152 may include features that can use data from comma-separated values (CSV) and MongoDB and be implemented using PowerShell and NODE.js, such as data visualization, analysis, bonus dashboards, risk boards, and artificial intelligence for IT operations (AIOPS).

[0059] The DCS 151 may include features such as APIs, software development kits (SDKs), and other toolkits developed and supported by the vendor. The DCS 151 may further provide data collection, structuring, and post-processing scripting capabilities. In addition, the DCS 151 may provide AIOPS based on storage management standards. For example, the DCS 151 can be used in any type of system such as servers, operating systems, or storage devices. The DCS 151 can be a script or a collection of scripts for logging into the system and collecting one or more characteristics of the system when necessary. For example, the DCS 151 can collect data related to the utilization of the system storage space. The DCS 151 may also include logs for tracking event errors, successes, and / or failures for code auditing and enhancement.

[0060] The business logic 152 may provide business profiles for data enrichment. A script or a collection of scripts can read data from the DCS 151 and use logic bound to the line of business (LOB) (e.g., by interacting with the web application 164) to convert the data read from the DCS 151 into information. The business logic 152 may use the structured data saved to the database or saved as a comma-separated value (CSV) file for the web application 164.

[0061] The web application 164 may provide information such as device capacity, hardware health, performance, bonus dashboards, and service level agreement (SLA) meters in an easy-to-view form. The web application 164 may provide a series of tools and code to interpret the data from the business logic 152 in tabular and / or graphical forms.

[0062] The DCS 151 can be regarded as a data collector from assets. Scripts in any programming language that can implement certain application programming interface (API) operations such as "get" and "put" can be placed in the server. Data collection can be scheduled as needed according to the urgency of the data. The data can be used for many different types of analysis due to its interrelatedness. The system is platform-independent, so components can be developed and implemented independently as long as the output of the components conforms to a common architecture.

[0063] Data structuring may include collecting data from assets using methods such as API calls and formatting the collected data into a tabular format with standard header names. The output can be created as a file and saved to database 153. The system may include other automation techniques to verify the collected data before use. Data transformation can be targeted for specific business applications, and the collected data can be enriched. Information visualization can be performed using web application 164. Implementation results can be captured for auditing and other business workflows.

[0064] DCS151 can collect data from multiple assets using a "fetch" operation. The collected data can be centralized, verified, and saved to database 153, and then transformed into a web page for display in web application 164. DCS151 can also generate a response file using a "place" operation based on additions to the workflow in the ticketing tool, where data transformation is performed as needed and saved to a file, and the asset configuration is changed using configuration change server 173. Additionally, the response file can link the ticketing tool to system 100, where parameters from both workflow additions and data collection can be verified separately for execution.

[0065] For example, the data from each asset may include MasterClass: {type: String, Required: true, default: 'Storage'}, DC: {type: String, required: false, default: false}, StorageType: {type: String, required: false, default: false}, DeviceName: {type: String, required: false, default: false, unique: true}, NodeName: {type: String, required: false, default: false}, SerialNumber: {type: String, required: false, default: false}, IP: {type: String, required: false, default: false}, VIP: {type: String, required: false, default: false}, ENV: {type: String, required: false, default: false}, Status: {type: String, required: false, default: false}, IsMaster: {type: String, required: false, default: false}, Manufacturer: {type: String, required: false, default: false}, Vendor: {type: String, required: false, default: false}, Model: {type: String, required: false, default: false}, ContractEndDate: {type: String, required: false, default: false}, ManagementTool: {type: String, required: false, default: false}, RackLocation: {type: String, required: false, default: false}, LoginThrough: {type: String, required: false, default: false}, UserName: {type: String, required: false,default: "NA"}, Legend: {type: String, required: false, default: false}, BU: {type: String, required: false, default: false}, DataManagerGroup: {type: String, required: false, default: false}, DataApprovalGroup: {type: String, required: false, default: false}, SupportGroup: {type: String, required: false, default: false}, ChangeManagementGroup: {type: String, required: false, default: "Change Management-Global"}, DCAddress: {type: String, required: false, default: false}, LastUpdated: {type: Date, required: false, default: Date.now}, LastUpdatedBy: {type: String, required: false, default: "System"}, IsAnAsset: {type: String, required: false, default: "No"}, AssetTag: {type: String, required: false, default: false}.,

[0066] Figure 2 Shows an example asset link diagram 200 according to one or more embodiments.

[0067] Assets can be linked to other assets through various data. For example, the storage asset 201 can be linked to the computer asset 202 through the volume unique identifier 211. The computer asset 202 can be linked to the operating system asset 203 through the guest identifier 212. The operating system asset 203 can be linked to the database asset 204 through the guest name 213. The database asset 204 can be linked to the application asset 205 through the database name 214.

[0068] Linked assets can be executed by the association engine. In the association engine, the master attribute "device name" can be used to appropriately tag data from different sources. For example, the master attribute "device name" can exist in inventory data, sub - fusion infrastructure, and edge - fusion infrastructure. Assets can be linked using master relationships, application bindings, ticket records, network records, or backup records. Master relationships can create associations between assets using boundary data. In application bindings, application information is captured using the hash tag or comment section of the sub - fusion infrastructure. For ticket records, the fusion infrastructure project name can be used to associate event changes or problem records of devices (virtual or physical). Network records can use the network characteristics (network - related attributes) of devices to associate all upstream and downstream connections of assets. Computer assets can adopt backup records.

[0069] Figure 3 Shows an example storage inventory user interface according to one or more embodiments.

[0070] The storage inventory user interface 300 can include data 310. The data 310 can include information retrieved from various assets in the network information technology infrastructure. For example, the data 310 can include device name, serial number, IP address, physical location, network location, user name, or manufacturer. The data 310 can be edited in the storage inventory user interface 300.

[0071] Figure 4 Shows an example user interface according to one or more embodiments.

[0072] The user interface 400 can include mapping data of assets. The mapping data can include information for linking various assets in the network information technology infrastructure. For example, as Figure 4 shown, the virtual machine 410 can be linked to the storage asset 420, computer asset 430, virtual machine asset 440, and database asset 450. The storage asset 420 can include information related to the volume 421, the computer asset 430 can include information related to the differentiated service 431, the virtual machine asset 440 can include information related to the virtual machine 441, and the database asset 450 can include information related to the database 451.

[0073] Figure 5 Is a block diagram showing an example process logic flow for providing an interface for mapping relationships between assets in a network information technology infrastructure according to one or more embodiments.

[0074] For example, the system 100 can include the network application 164, the inventory user interface 300, and / or the user interface 400.

[0075] Method 500 may include various operations performed by at least one processor 602 of system 100. The various operations may include sending a query including an asset identifier (operation 510). The various operations may include receiving a data structure of the asset, where the data structure includes determined relationships between the asset and other hardware and software assets (operation 520). The various operations may include rendering the data structure into a format for display (operation 530). The various operations may include displaying the rendered data structure (operation 540). The various operations may include associating a display color with the asset based on information in a ticketing tool (operation 550). The various operations may include determining support members of the asset and displaying the determined support members (operation 560).

[0076] Applying a linking algorithm to standardized data copied from a response file generated by an asset in response to an instruction sent to the asset, the data structure may be created based on the linking algorithm, and the standardized data copied from the response file may be verified based on a logging event associated with copying the standardized data from the response file. A query may be sent to an external application. The asset may include one or more of a storage asset 201, a computer asset 202, an operating system asset 203, a database asset 204, or an application asset 205. The determined relationships may include one or more of a storage asset 201 linked to a computer asset 202 by a volume unique identifier 211, a computer asset 202 linked to an operating system asset 203 by a guest identifier 212, an operating system asset 203 linked to a database asset 204 by a guest name 213, or a database asset 204 linked to an application asset 205 by a database name 214. Data changes may be verified by prompting approval team members to verify data from the response file. The response file may include one or more of volume characteristics of a storage asset 201, virtual machine information of a computer asset 202, virtual disk information of a computer asset 202, physical storage information of a computer asset 202, guest server information of a database asset 204, database size information of a database asset 204, database name information of a database asset 204, or database disk associations of a database asset 204. The query may be sent via a uniform resource locator, and the data structure may be received from the external application via JavaScript Object Notation.

[0077] The DCS151 can log in to an asset using a script and generate an asset response file as a volatile or non-volatile instance. The DCS151 can use an API to collect data from the generated response file into volatile or non-volatile memory. The DCS151 can track collection events (indicating errors or successes) and log these events into a ticketing tool (not shown) for auditing. The DCS151 can use the logged events to verify the collected data. The business logic 152 can read the verification data from volatile memory, determine standard report data from the read asset data, and save the standardized data in the formatted structure of the asset in the database 153. In response to a user's query of the database 153, the web application 164 can display the saved data in a graphical user interface (such as a web UI).

[0078] The web application 164 can display the standard format data in various group configurations. For example, the standard format data can be displayed as separate web interfaces for different geographical regions or networks.

[0079] In one or more embodiments, a user can input configuration changes requested for a vendor storage device into the ticketing tool. The configuration change server 173 can use the asset API to log in to the asset using a username and password. The configuration change server 173 can convert the requested configuration changes from the ticketing tool into an asset-specific format and update the asset with the asset-specific format configuration changes. The configuration change server 173 can query the asset to determine whether the configuration has been successfully applied and log the configuration changes. The configuration change server 173 can provide a message to the ticketing tool indicating that the requested configuration changes have been successfully applied.

[0080] When dealing with different assets, the assets have different ways of interpreting similar data, which may confuse and / or delay the response of system administrators. Through data standardization, system administrators and others can more easily read the data and take appropriate actions. For example, an API or Secure Shell protocol (SSH) can be used to collect data. The collected data can be formatted so that the data representing asset-specific terms is converted into an industry-standard form. A LOB threshold can be applied to the data for analysis, enriching and validating the information, and capturing execution logs. The final data can be converted into CSV UTF-8 format and saved locally for general access by the web application 164. The data can be used for deduplication and / or snapshot interpretation. The standardized data can be visualized as a chart, where violations of LOB rules can be reflected to ensure operational stability. For go / no-go scenarios, the standardized data can be used during implementation to avoid asset-related issues.

[0081] Figure 6Shows an embodiment of a general-purpose computer system that can execute the technology described in the present invention.

[0082] Unless otherwise specifically stated, it will be apparent from the following discussion that throughout the discussion of the specification, it should be understood that the terms "processing", "operation", "computation", "determination", "analysis", or similar terms refer to the operations and / or processes of a computer or computing system or similar electronic computing device that operate on and / or transform data represented in a physical quantity (such as an electronic quantity) into other data also represented in a physical quantity.

[0083] Similarly, the term "processor" can refer to any device or part of a device that processes electronic data, for example, processes electronic data from registers and / or memory and transforms the electronic data into other electronic data, such as other electronic data that can be stored in registers and / or memory. A "computer", "computing machine", "computing platform", "computing device", or "server" can include one or more processors.

[0084] Figure 6 Shows an implementation of computer system 600. Computer system 600 can include a set of instructions that, when executed, can cause computer system 600 to perform any one or more of the methods or computer-based functions disclosed in the present invention. Computer system 600 can operate as a stand-alone device or can be connected to other computer systems or peripheral devices using a network or the like.

[0085] In a network deployment, computer system 600 can operate as a server, or as a client user computer in a server-client user network environment, or as a peer computer system in a peer-to-peer (or distributed) network environment. Computer system 600 can also be implemented as various devices or integrated into various devices, such as a personal computer (PC), tablet computer, set-top box (STB), personal digital assistant (PDA), mobile device, palmtop computer, laptop computer, desktop computer, communication device, wireless phone, landline phone, control system, camera, scanner, fax machine, printer, pager, personal trusted device, World Wide Web device, network router, switch, or bridge, or any other machine capable of executing a set of instructions (sequential instructions or other instructions). In a particular embodiment, computer system 600 can be implemented using an electronic device that provides voice, video, or data communication. Additionally, although computer system 600 is shown as a single system, the term "system" should also be considered to include any collection of systems or subsystems that can individually or jointly execute a set or multiple sets of instructions to perform one or more computer functions.

[0086] As Figure 6As shown, computer system 600 may include a processor 602, such as a central processing unit (CPU), a graphics processing unit (GPU), or both. Processor 602 may be a component in various systems. For example, processor 602 may be part of a standard personal computer or workstation. Processor 602 may be one or more general-purpose processors, digital signal processors, application-specific integrated circuits, field-programmable gate arrays, servers, networks, digital circuits, analog circuits, and combinations thereof, or other data analysis and processing devices known now or developed later. Processor 602 may execute software programs, such as manually generated (i.e., programmed) code.

[0087] Computer system 600 may include a memory 604 that can communicate via a bus 608. Memory 604 may be a main memory, a static memory, or a dynamic memory. Memory 604 may include, but is not limited to, computer-readable storage media, such as various types of volatile and non-volatile storage media, including but not limited to random access memory, read-only memory, programmable read-only memory, electrically programmable read-only memory, electrically erasable read-only memory, flash memory, magnetic tapes or disks, optical media, etc. In one embodiment, memory 604 includes a cache or random access memory of processor 602. In an alternative embodiment, memory 604 is separate from processor 602 (e.g., the cache memory of the processor, system memory, or other memory). Memory 604 may be an external storage device or database for storing data. Examples include hard disk drives, compact discs ("CDs"), digital video discs ("DVDs"), memory cards, memory sticks, floppy disks, universal serial bus ("USB") storage devices, or any other device that can be used to store data. Memory 604 may be used to store instructions executable by processor 602. The functions, behaviors, or tasks shown in the figure or described in the present invention may be executed by processor 602 that executes instructions stored in memory 604. These functions, behaviors, or tasks are independent of a specific type of instruction set, storage medium, processor, or processing strategy and may be executed alone or jointly by software, hardware, integrated circuits, firmware, microcode, etc. Similarly, the processing strategy may include multiprocessing, multitasking, parallel processing, etc.

[0088] As shown in the figure, computer system 600 may further include a display 610, such as a liquid crystal display (LCD), an organic light-emitting diode (OLED), a flat panel display, a solid-state display, a cathode ray tube (CRT), a projector, a printer, or other display devices known now or developed later for outputting the determined information. Display 610 may serve as an interface for a user to view the operation of processor 602, or specifically as an interface to the software stored in memory 604 or drive unit 606.

[0089] Additionally or alternatively, computer system 600 may include an input device 612 that allows a user to interact with any component of computer system 600. Input device 612 can be a numeric keypad, a keyboard, or a cursor control device such as a mouse, a joystick, a touch screen display, a remote control, or any other device that interacts with computer system 600.

[0090] Computer system 600 may also include or alternatively include a drive unit 606 implemented as a disk or optical drive. Drive unit 606 may include a computer-readable medium 622 in which a set or multiple sets of instructions 624, such as software, may be embedded. Additionally, instructions 624 may embody one or more of the methods or logics described in the present invention. During execution by computer system 600, instructions 624 may be located entirely or partially in memory 604 and / or processor 602. As described above, memory 604 and processor 602 may also include computer-readable media.

[0091] In some systems, computer-readable medium 622 includes instructions 624, or receives and executes instructions 624 in response to a propagated signal, such that a device connected to network 670 can communicate voice, video, audio, images, or any other data over network 670. Additionally, instructions 624 may be transmitted or received over network 670 via communication port or interface 620 and / or using bus 608. Communication port or interface 620 may be part of processor 602 or a separate component. Communication port or interface 620 may be created in software or may be a physical connection in hardware. Communication port or interface 620 may be connected to network 670, an external medium, display 610, or any other component or combination thereof in computer system 600. The connection to network 670 may be a physical connection, such as a wired Ethernet connection, or may be established wirelessly, as described below. Similarly, additional connections to other components of computer system 600 may be physical or may be established wirelessly. Network 670 may alternatively be directly connected to bus 608.

[0092] Although computer-readable medium 622 is shown as a single medium, the term "computer-readable medium" may include a single medium or multiple media, such as a centralized or distributed database, and / or associated caches and servers that store a set or multiple sets of instructions. The term "computer-readable medium" may also include any medium that can store, encode, or carry a set of instructions that can be executed by a processor or that cause a computer system to perform any one or more of the methods or operations disclosed in the present invention. Computer-readable medium 622 may be a non-transitory computer-readable medium or a tangible computer-readable medium.

[0093] The computer-readable medium 622 may include solid-state memory such as a memory card or other package that includes one or more non-volatile read-only memories. The computer-readable medium 622 may be random access memory or other volatile rewritable memory. Additionally or alternatively, the computer-readable medium 622 may include magneto-optical or optical media such as a disk, tape, or other storage device for capturing carrier signals such as signals communicated through a transmission medium. Digital file attachments of e-mails or other independent information files or sets of files may be considered distribution media, i.e., tangible storage media. Accordingly, the present disclosure may be considered to include any one or more of computer-readable media or distribution media and other equivalent media and successor media that can be used to store data or instructions.

[0094] In alternative embodiments, dedicated hardware implementations such as application specific integrated circuits, programmable logic arrays, and other hardware devices may be constructed to implement one or more of the methods described herein. Applications that may include devices and systems of various embodiments may broadly include a variety of electronic and computer systems. One or more of the embodiments described herein may be implemented using two or more specific interconnected hardware modules or devices that use related control and data signals that may be communicated between or through the modules or as part of an application specific integrated circuit. Accordingly, the system includes software, firmware, and hardware implementations.

[0095] The computer system 600 may be connected to a network 670. The network 670 may define one or more networks, including wired or wireless networks. The wireless network may be a cellular telephone network, 802.11, 802.16, 802.20, or WiMAX network. Additionally, such networks may include public networks (such as the Internet), private networks (such as an intranet), or combinations thereof, and may utilize a variety of network protocols, including but not limited to TCP / IP-based network protocols, existing or later developed. The network 670 may include a wide area network (WAN) (such as the Internet), a local area network (LAN), a campus network, a metropolitan area network, a direct connection (such as through a universal serial bus (USB) port), or any other network capable of data communication. The network 670 may couple one computing device to another to enable data communication between the devices. The network 670 may generally employ any form of machine-readable medium for communicating information from one device to another. The network 670 may include a communication method for transmitting information between computing devices. The network 670 may be divided into multiple sub-networks. The sub-network may allow access to all other components connected thereto or restrict access between components. The network 670 may be considered a public or private network connection and may include virtual private networks or encryption or other security mechanisms used over the public Internet, etc.

[0096] According to various embodiments of the present disclosure, the methods described in the present disclosure can be implemented by software programs executable by a computer system. In addition, in exemplary, non-limiting embodiments, the embodiments may include distributed processing, component / object distributed processing, and parallel processing. Alternatively, a virtual computer system processing can be constructed to implement one or more of the methods or functions described in the present invention.

[0097] Although this specification describes components and functions that can be implemented in specific embodiments with reference to specific standards and protocols, the present disclosure is not limited to such standards and protocols. For example, Internet and other packet-switching network transmission standards (such as TCP / IP, UDP / IP, HTML, HTTP) are examples of the current state of the art. Such standards are periodically replaced by equivalent standards with substantially the same functions, faster speeds, or higher efficiencies. Accordingly, alternative standards and protocols having the same or similar functions as the standards and protocols disclosed in the present invention can be considered equivalent to them.

[0098] It should be understood that in one embodiment, the method steps are performed by a suitable processor (or processors) of a processing (i.e., computer) system by executing instructions (computer-readable code) stored in a memory. It should also be understood that the present disclosure is not limited to any specific embodiment or programming technique, and the present disclosure can be implemented using any suitable technique to achieve the functions described in the present invention. The present disclosure is not limited to any specific programming language or operating system.

[0099] Figure 7 Example table 700 showing a user interface according to one or more embodiments. The temperature report may include colors associated with various different severity levels, such as red, orange, yellow, and green.

[0100] As Figure 7 shown, table 700 can be a lookup table, and different input combinations from the asset status and ticketing tool provide different results for the final display color of the asset. For example, example table 700 shows the relevant temperatures of various entities associated with the asset and various tickets associated with the asset. The resulting final color for each row is based on the combination of all relevant temperatures in that row.

[0101] The user interface 400 can be integrated with the ticketing tool and can provide a temperature report or a heat map. For example, the user interface 400 can use mapped data to query the ticketing tool to collect events, changes, and issues generated for an asset within a specified time period (such as the past seven days) or under a minimum ticket count (such as ten tickets).

[0102] The query can discover previous problems and determine the health status of the asset. For temperature reports, the operating status of any one of the numerous redundant logical links can highlight the search results in yellow. The operating status of any one of the numerous redundant hardware links can highlight the search results in orange. For temperature reports, except for online, the status of any single point of failure item can highlight the search results in red.

[0103] In the ticketing tool, a severity level can be assigned to an event, such as P1, P2, and P3, where P1 is the most severe event. The user interface 400 can assign various colors to temperature reports. For example, the user interface 400 can highlight in yellow events with a severity level of P2 or above that have been closed in the past 7 days. The user interface 400 can highlight in yellow persistent problems with an event severity level of P3 or below. The user interface 400 can highlight in orange persistent problems with an event severity level of P2 or above. The user interface 400 can highlight in orange persistent change tickets. The user interface 400 can highlight in red persistent events with an event severity level of P2 or above.

[0104] As Figure 7 shown, the colors of the results available for display can be based on combinations of other colors. The example table 700 can also utilize additional logic to determine the specific color of the results. For example, a disk asset can be coded yellow when there are more than 75 associated events, orange when there are more than 85 events, and red when there are more than 90 events.

[0105] Figure 8 Another example table 800 of the user interface according to one or more embodiments is shown.

[0106] As Figure 8 shown, based on the type and changes of the problem event, the user interface 400 can determine the support team or the primary team of the asset and can identify the members who have handled this problem. The user interface 400 can determine the secondary team of the asset based on the member participation count of the ticket. The user interface 400 can determine the support team (the people most suitable for handling the ticket) based on the direct participation of members in the ticket and the update count mentioned in the ticket.

[0107] If the user interface 400 cannot determine the support group for the primary asset based on the direct participation of the members of the ticket and the update count mentioned in the ticket, the user interface 400 can determine the support group members who contribute the most to any other asset linked to the primary asset, such as a preference filter (in descending order) set by the same model, manufacturer, or device category. The user interface 400 can also filter the members based on the time zone to align the correct members based on availability. The user interface 400 can determine availability through an understanding mode, but it sorts the support members based on contribution and then by time.

[0108] The user interface 400 can store the determined support group and support members in table 800.

[0109] Figure 9 Another example user interface according to one or more embodiments is shown.

[0110] As Figure 9 shown, the user interface 900 can include information about the primary asset. This information can include a list of tickets 910 associated with storage assets linked to the primary asset, a list of tickets 920 associated with computer assets linked to the primary asset, a heat map 930 associated with storage assets linked to the primary asset, and a heat map 940 associated with computer assets linked to the primary asset. As Figure 9 shown, this information can be provided on different tabs in the user interface 900, but the present disclosure is not limited thereto.

[0111] The technology disclosed in the present disclosure achieves a technological improvement by providing centralized asset management and mapping tools required for global infrastructure operations. The centralized asset management and mapping tools provide the health and readiness status of assets, the relationships between assets, asset issue tracking, asset events, and configuration change history. Accordingly, the mapping of assets and operations is improved. The technology disclosed in the present disclosure provides a lookup table or reference diagram to find the blast radius of configuration items when an asset has a problem.

[0112] The technology disclosed in the present disclosure creates a functional configuration management database, enabling enterprises to avoid significant investments in underlying infrastructure, professional services, and licenses. The technology disclosed in the present disclosure allows comprehensive infrastructure management teams to investigate problems, reducing delays in problem-solving. The technology disclosed in the present disclosure can identify the correct configuration items, provide efficient investigations, and reduce the overall delay in problem-solving.

[0113] Those skilled in the art will recognize that the above and other embodiments of the described systems and methods may be employed. The descriptions of the various systems and methods above are intended to provide specific examples of certain ways of making and using the systems disclosed and described herein. These descriptions are not intended to, nor should they be construed as, an exhaustive list of the possible ways of making and using the systems. Numerous modifications may be made thereto, including substitutions of systems between examples and variations between combinations. After reading this disclosure, those of ordinary skill in the art should be able to make these modifications and changes with ease.

[0114] The disclosed systems, apparatuses, devices, and methods are illustrated herein by way of example and with reference to the accompanying drawings. The examples discussed herein are for reference only and are intended to assist in explaining the apparatuses, devices, systems, and methods described herein. For any particular implementation of any of the apparatuses, devices, systems, or methods, the functions or components shown in the drawings or discussed below should not be considered mandatory, except where specifically designated as mandatory. For ease of reading and clarity, certain components, modules, or methods may be described separately in connection with a particular drawing. In this disclosure, any identification of a particular technology, arrangement, etc. is related to the specific examples presented and may also be merely a general description of such technology, arrangement, etc. Unless specifically specified, references to specific details or examples are not intended to, nor should they be construed as, mandatory or restrictive. Any failure to specifically describe a combination or sub - combination of components should not be construed as indicating that any combination or sub - combination is not feasible. It should be understood that the examples, arrangements, configurations, components, elements, apparatuses, devices, systems, methods, etc. disclosed and described may be modified and that modifications may be required for a particular application. Further, for any of the methods described, whether or not illustrated in conjunction with a flowchart, it should be understood that, unless otherwise specified or the context requires, any explicit or implicit ordering of the steps performed during the execution of the method does not mean that the steps must be performed in the given order, but rather that the steps may be performed in a different order or simultaneously.

[0115] The phrases “various embodiments,” “some embodiments,” “an embodiment,” “some exemplary embodiments,” “an exemplary embodiment,” or “a certain embodiment” referred to throughout this specification mean that at least one embodiment includes the specific features, structures, or characteristics described in connection with any embodiment. Thus, the phrases “in various embodiments,” “in some embodiments,” “in an embodiment,” “in some exemplary embodiments,” “in an exemplary embodiment,” or “in a certain embodiment” that appear throughout this specification do not necessarily all refer to the same embodiments. Additionally, the specific features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0116] As used throughout this disclosure, components or modules generally refer to products that are logically combinable to perform a function or a related group of functions. Like reference numerals generally denote the same or similar components. Components and modules may be implemented in software, hardware, or a combination of software and hardware. The term "software" is used broadly and encompasses both executable code such as machine-executable or machine-interpretable instructions, and data structures, data repositories, and computing instructions stored in any suitable electronic format, including firmware and embedded software. The terms "information" and "data" are used broadly and encompass a variety of electronic information, including executable code; content such as text, video data, and audio data; and various codes or markers. Where the context permits, the terms "information," "data," and "content" may sometimes be used interchangeably. It should be noted that although, for clarity and to aid understanding, some examples discussed herein may describe a particular feature or function as part of a particular component or module, or as existing at a particular layer of a computing device (e.g., the hardware layer, the operating system layer, or the application layer), such features or functions may be implemented as part of different components or modules or operate at different layers of the communication protocol stack. Those of ordinary skill in the art will recognize that the systems, apparatus, devices, and methods described herein may be used with other types of devices or, with simple modifications, may be made to work with other types of devices, may employ other computing system arrangements such as client-server distributed systems, and may operate using other protocols than those described or at other layers of the communication protocol stack.

[0117] This specification and the examples are for illustrative purposes only, and the appended claims indicate the actual scope and spirit of the disclosure.

Claims

1. A method, comprising: performing the following operations by at least one processor: sending a query including an asset identifier; receiving a data structure of the asset, wherein the data structure includes determined relationships between the asset and other hardware and software assets; rendering the data structure into a format for display; displaying the rendered data structure.

2. The method according to claim 1, wherein applying a linking algorithm to standardized data copied from a response file generated by an asset in response to an instruction sent to the asset, creating the data structure based on the linking algorithm, and validating the standardized data copied from the response file based on a logging event associated with copying the standardized data from the response file.

3. The method according to claim 1, wherein the sending of the query includes sending the query to an external application.

4. The method according to claim 1, wherein the asset includes one or more of a storage asset, a computer asset, an operating system asset, a database asset, or an application asset.

5. The method according to claim 1, wherein the determined relationships include one or more of a storage asset linked to a computer asset by a volume unique identifier, a computer asset linked to an operating system asset by a guest identifier, an operating system asset linked to a database asset by a guest name, or a database asset linked to an application asset by a database name.

6. The method according to claim 2, wherein validating the data from the response file by prompting approval team members to validate data changes.

7. The method according to claim 1, wherein the displaying of the rendered data structure includes associating a display color with the asset based on information in a ticketing tool.

8. The method according to claim 2, wherein the response file includes one or more of volume characteristics of a storage asset, virtual machine information of a computer asset, virtual disk information of a computer asset, physical storage information of a computer asset, guest server information of a database asset, database size information of a database asset, database name information of a database asset, or database disk association of a database asset.

9. The method according to claim 1, wherein the displaying of the rendered data structure includes determining support members of the asset and displaying the determined support members.

10. The method according to claim 1, wherein the sending of the query includes sending the query via a Uniform Resource Locator; wherein the receiving of the data structure includes receiving the data structure from an external application via JavaScript Object Notation.

11. A system, comprising: a memory that can store instructions; at least one processor that can execute the stored instructions to perform a method including the following steps: sending a query including an asset identifier; receiving a data structure of the asset, wherein the data structure includes determined relationships between the asset and other hardware and software assets; rendering the data structure into a format for display; Display the rendered data structure.

12. The system according to claim 11, wherein the linking algorithm is applied to the standardized data copied from the response file generated by the asset in response to the instruction sent to the asset, and the data structure is created based on the linking algorithm, wherein the standardized data copied from the response file is verified based on the logging event associated with copying the standardized data from the response file.

13. The system according to claim 11, wherein the sending of the query includes sending a query to an external application.

14. The system according to claim 11, wherein the asset includes one or more of a storage asset, a computer asset, an operating system asset, a database asset, or an application asset.

15. The system according to claim 11, wherein the determining of the relationship includes one or more of a storage asset linked to a computer asset by a volume unique identifier, a computer asset linked to an operating system asset by a guest identifier, an operating system asset linked to a database asset by a guest name, or a database asset linked to an application asset by a database name.

16. The system according to claim 12, wherein the data from the response file is verified by prompting approval team members to verify the data change.

17. The system according to claim 11, wherein the displaying of the rendered data structure includes associating a display color with the asset based on the information in the ticketing tool.

18. The system according to claim 12, wherein the response file includes one or more of the volume characteristics of the storage asset, the virtual machine information of the computer asset, the virtual disk information of the computer asset, the physical storage information of the computer asset, the guest server information of the database asset, the database size information of the database asset, the database name information of the database asset, or the database disk association of the database asset.

19. The system according to claim 11, wherein the displaying of the rendered data structure includes determining the support members of the asset and displaying the determined support members.

20. A non-transitory computer-readable medium storing instructions that, when executed by at least one processor, cause the at least one processor to perform a method comprising the steps of: sending a query including an asset identifier; receiving the data structure of the asset, wherein the data structure includes the determined relationship between the asset and other hardware and software assets; rendering the data structure into a format suitable for display; displaying the rendered data structure.

Images