Computerized systems and methods for automatically detecting anomalies in distributed SCADA systems and thereby dynamically displaying a unified interface.

Abstract

Systems and methods for improving interaction with computers or between computers in content delivery, search, and / or hosting systems supported or configured by devices, servers, and / or platforms are disclosed. The disclosed systems and methods provide a novel framework for automatically generating and dynamically updating interactive user interfaces (UIs) that include digital information related to multiple processes and operations. The UI provides consistent functionality across platforms, devices, and / or services used to view the UI and / or interface objects (e.g., tiles) and / or interact with the UI and / or interface objects (e.g., tiles). The UI provides dynamic mechanisms for controlling assets, as well as mechanisms for comparing data from different assets (therefore, some assets can subsequently be manipulated). The UI enables the detection and contextualized visualization of operational data for assets and / or locations in distributed Supervisory Control and Data Acquisition (SCADA) systems in cloud-connected environments.

Description

[0001] This application includes copyrighted material. The copyright holder does not object to anyone making fax copies of the patent disclosure as it appears in Patent and Trademark Office documents or records, but otherwise reserves all copyright rights.

[0002] Cross-references to related applications

[0003] This application claims priority to U.S. Provisional Application No. 62 / 934,082, filed November 12, 2019, entitled “Reporting Anomalies in Distributed SCADA Server and System,” which is incorporated herein by reference in its entirety. Technical Field

[0004] Some embodiments generally relate to improving the performance of network-based computerized content hosting and delivery devices, systems, and / or platforms by: novel and improved asset management and visualization framework modification capabilities for automatically detecting anomalies in distributed SCADA systems and thereby dynamically displaying a unified interface, and providing non-native functionality to such devices, systems, and / or platforms. Background Technology

[0005] As more data is logged into databases, cloud servers, operational history, and / or any other type of software-based and hardware-supported local and / or network-configured data repositories, customers, along with their associated systems and services, are looking for computerized mechanisms to manage, understand, and display that data.

[0006] Traditional mechanisms are failing because they are leading to data loss, increased bottlenecks and inefficiencies in data reception and presentation, and a general lack of organization in how data is protected, provided, and displayed to users. Furthermore, mishandling of assets, asset data, and operations as a whole has resulted in reduced task efficiency and unnecessary resource exhaustion. Summary of the Invention

[0007] The failure of existing technologies in the field of computerized data storage, preservation, and presentation is the current lack of online or computerized mechanisms that enable automated, dynamic determination and updating of interactions to determine how and in what way data is compiled, presented, and / or interacted with. Among other features, exposed systems and methods provide an open framework for asset management and visualization to address these and more needs.

[0008] According to some embodiments, the disclosed framework implements systems and methods for automatically generating and updating interactive user interfaces (UIs) that include digital information related to multiple processes and operations. The UI provides consistent functionality across platforms, devices, and / or services used to view the UI and / or the interface objects included therein and / or interact with the UI and / or the interface objects included therein. The UI provides dynamic mechanisms for controlling assets, as well as mechanisms for comparing data of different assets (thereby allowing some assets to be manipulated).

[0009] In some embodiments, the disclosed systems and methods provide electronic mechanisms for interactively detecting and reporting anomalies in a distributed Supervisory Control and Data Acquisition (SCADA) system within a cloud-connected environment. The disclosed UI framework enables novel mechanisms for data monitoring and asset or location (e.g., plant) control using a unified UI disclosed herein.

[0010] In some embodiments, the UI provides contextualized visualizations of exceptions and anomalies relevant to their area of ​​control, allowing operators to focus more on these exceptions and anomalies without having to sift through large amounts of data.

[0011] In some embodiments, the UI provides electronic filtering and navigation capabilities for asset / location data, enabling users to identify another area of ​​the plant or similar situations in the past.

[0012] In some embodiments, asset / location data, as well as filtering and navigation history for specific users and / or tasks, may be stored, for example, in a cache. Caching of data allows for continuous operation in intermittently connected scenarios. In some embodiments, collected and cached anomalies may be detected and / or stored from cloud data (e.g., analysis of data transmitted to, stored in, or retrieved from cloud servers or associated data repositories).

[0013] Some embodiments include visualization of asset-based anomalies. Some embodiments include connected and disconnected systems. Some embodiments include distributed asset systems. Some embodiments include configurable filtering and visualization. In some embodiments, the display may be associated with the SCADA navigation context.

[0014] Some embodiments include contextualized asset-based news. As discussed herein, news can be configured as interface objects depicted within a public UI. Such news can be associated with a specific asset, job, task or operation, location, user, or some combination thereof. For example, news could correspond to an anomaly detected in an asset's operation.

[0015] In some embodiments, the exposed UI framework can be implemented as an information push client control module that can be integrated into the system platform's Human-Machine Interface (HMI). The UI of the HMI is configured as a tool that, for example, operators and production line supervisors can use to coordinate and control industrial and manufacturing processes and machines. The HMI transforms complex process variables into usable and actionable information.

[0016] In some embodiments, the UI framework may be a centralized cloud-based or web-based interface that can be accessed and utilized by client systems from a remote location.

[0017] According to some embodiments, a computer-implemented method is disclosed that automatically detects anomalies in a distributed SCADA system and thereby dynamically displays a unified interface.

[0018] Some embodiments provide a non-transitory computer-readable storage medium for performing technical steps of the framework described above. The non-transitory computer-readable storage medium tangibly stores or tangibly encodes computer-readable instructions thereon that, when executed by a device (e.g., an application server, messaging server, email server, advertising server, content server, and / or client device, etc.), cause at least one processor to execute a novel and improved framework for detecting anomalies in a distributed SCADA system and thereby dynamically displaying a unified interface.

[0019] According to one or more embodiments, a system is provided that includes one or more computing devices configured to provide functionality according to such embodiments. According to one or more embodiments, functionality is implemented in steps of a method performed by at least one computing device. According to one or more embodiments, program code (or program logic) is implemented on a non-transitory computer-readable medium, executed by a processor of the computing device, to implement functionality according to one or more such embodiments.

[0020] According to some embodiments, a computing device is disclosed, the computing device comprising: one or more processors; and a non-transitory computer-readable storage medium storing computer-executable instructions therein, the computer-executable instructions, when executed by the one or more processors, causing the one or more processors to perform actions that display a user interface (UI), the actions including: receiving electronic data via a network relating to the operation of a physical asset at a location, the electronic data representing at least one detected anomaly of the asset during a time period; creating the UI, the UI including functionality for visually displaying the received electronic data as interactive digital content; displaying the UI on a display of a client computing device via the network; receiving from the client computing device a request to filter the displayed electronic data; modifying the UI based on the filtering request, the modification causing the UI to automatically change the quantity and type of interactive digital content displayed within the UI; receiving via the network input from a second client device for a portion of the modified digital content, the portion corresponding to an anomaly of the asset; and electronically establishing an electronic connection via the network between the client device and a device associated with the asset and the location, the established connection including functionality enabling the client device to control the asset via the network through the modified UI.

[0021] In some embodiments, the action further includes storing the electronic data in a cloud-based network cache, wherein receiving the electronic data includes retrieving the electronic data from the cache.

[0022] In some embodiments, the control includes executing an application via the network through the UI, the application performing maintenance operations on the asset.

[0023] In some embodiments, the filtering request is in response to interaction with at least a portion of the interactive digital content. In some embodiments, the action further includes analyzing the electronic data of the asset; and automatically generating the filtering request based on the analysis without user input.

[0024] In some embodiments, the filtering request includes a set of criteria corresponding to the types of data included in the electronic data associated with the anomaly. In some embodiments, the filtering request enables navigation of specific types of asset data related to multiple locations.

[0025] In some embodiments, the electronic connection is established when the UI is first displayed on the client device.

[0026] In some embodiments, the action further includes collecting information relating to control of the asset. In some embodiments, the action further includes receiving a second set of electronic data based at least in part on the collected information.

[0027] In some embodiments, the action further includes collecting information related to the filtering request and the modification of the UI. In some embodiments, the action further includes receiving a second set of electronic data; and updating the UI based on the second set of electronic data and the collected information.

[0028] In some embodiments, the action further includes analyzing the received electronic data; and determining, based on the analysis, the type of display format of the electronic data, wherein the display of the electronic data within the UI is at least in part based on the determined type. Attached Figure Description

[0029] The foregoing and other objects, features, and advantages of this disclosure will become clear from the following description of embodiments illustrated in the accompanying drawings, in which reference numerals refer to the same parts throughout the various views. The drawings are not necessarily drawn to scale, but rather to emphasize the principles illustrating this disclosure:

[0030] Figure 1 This is a schematic diagram illustrating an example of a network that can implement the systems and methods disclosed herein, according to some embodiments of this disclosure;

[0031] Figure 2 This is a schematic diagram illustrating an example of a network that can implement the systems and methods disclosed herein, according to some embodiments of this disclosure;

[0032] Figure 3 A schematic diagram illustrating an example of a client device according to some embodiments of the present disclosure is provided.

[0033] Figure 4 This is a block diagram illustrating components of an exemplary system according to an embodiment of the present disclosure;

[0034] Figure 5 The illustrations depict non-limiting example embodiments of a UI and the functionality included therein, according to some embodiments of the present disclosure;

[0035] Figure 6 The illustrations depict non-limiting example embodiments of a UI and the functionality included therein, according to some embodiments of the present disclosure;

[0036] Figure 7 The illustrations depict non-limiting example embodiments of the functionality of interface objects within embodiments of a UI according to some embodiments of the present disclosure;

[0037] Figure 8The illustrations depict non-limiting example embodiments of the functionality of interface objects within embodiments of a UI according to some embodiments of the present disclosure;

[0038] Figure 9 The illustrations depict non-limiting example embodiments of the functionality of interface objects within embodiments of a UI according to some embodiments of the present disclosure;

[0039] Figure 10 The illustrations depict non-limiting example embodiments of a UI according to some embodiments of the present disclosure and the functions included therein; and

[0040] Figure 11 Non-limiting data streams according to some embodiments of this disclosure are described in detail. Detailed Implementation

[0041] This disclosure will now be described more fully below with reference to the accompanying drawings, which form part of this disclosure and illustrate certain exemplary embodiments by way of non-limiting description. However, the subject matter can be implemented in a variety of different forms, and therefore, the covered or claimed subject matter is intended to be construed as not being limited to any of the exemplary embodiments set forth herein; exemplary embodiments are provided merely for illustration. Similarly, a reasonably broad scope of the claimed or covered subject matter is contemplated. Among other things, the subject matter can also be implemented as a method, apparatus, component, or system, for example. Therefore, embodiments can take the form of, for example, hardware, software, firmware, or any combination thereof (other than software itself). Consequently, the following detailed description is not intended to be understood in a limiting sense.

[0042] Throughout the specification and claims, terminology may have nuanced meanings implied or suggested in the context beyond its expressly stated meaning. Similarly, the phrase "in some embodiments" as used herein does not necessarily refer to the same embodiment, and the phrase "in another embodiment" as used herein does not necessarily refer to a different embodiment. For example, the claimed subject matter is intended to include combinations of all or some of the exemplary embodiments.

[0043] Generally, terms can be understood, at least in part, from their use in context. For example, terms such as “and,” “or,” or “and / or,” as used herein, can include a variety of meanings that can depend, at least in part, on the context in which such terms are used. Typically, “or,” if used in an associative list such as A, B, or C, is intended to refer to A, B, and C used herein in an inclusive sense, and A, B, or C used herein in an exclusive sense. Furthermore, the term “one or more,” as used herein, depends, at least in part on the context, and can be used to describe any feature, structure, or characteristic in a singular sense, or can be used to describe a combination of features, structures, or characteristics in a plural sense. Similarly, terms such as “a,” “an,” or “the” can again be understood to convey either a singular or a plural usage, depending, at least in part, on the context. Moreover, the term “based on” can be understood not necessarily to convey an exclusive set of factors, but can allow for the presence of additional factors that are not necessarily explicitly expressed, again depending, at least in part, on the context.

[0044] The present disclosure is described below with reference to block diagrams and operational illustrations of methods and apparatus. It is understood that each block of a block diagram or operational illustration, and combinations of blocks in a block diagram or operational illustration, can be implemented by means of analog or digital hardware and computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer to modify its function as detailed herein, or to a special-purpose computer, ASIC, or other programmable data processing apparatus, such that instructions executed via a processor of the computer or other programmable data processing apparatus implement the function / action specified in one or more blocks of the block diagram or operational illustration. In some alternative implementations, the functions / actions marked in the blocks may not occur in the order indicated in the operational illustration. For example, two blocks shown consecutively may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order, depending on the functions / actions involved.

[0045] For the purposes of this disclosure, a non-transitory computer-readable medium (or one or more computer-readable storage media) stores computer data, which may include computer program code (or computer-executable instructions) in a machine-readable form that is executable by a computer. By way of example and not limitation, a computer-readable medium may include a computer-readable storage medium for tangible or fixed storage of data, or a communication medium for transient interpretation of a signal containing code. As used herein, a computer-readable storage medium means physical or tangible storage (as opposed to a signal) and includes, but is not limited to, volatile and non-volatile, removable and non-removable media implemented in any method or technology for tangible storage of information (such as computer-readable instructions, data structures, program modules or other data). Computer-readable storage media include, but are not limited to, RAM, ROM, EPROM, EEPROM, flash memory or other solid-state memory technologies, CD-ROM, DVD, or other optical storage, cloud storage, magnetic cassettes, magnetic tape, disk storage or other magnetic storage devices, or any other physical or material medium that can be used to tangibly store desired information or data or instructions and that can be accessed by a computer or processor.

[0046] For the purposes of this disclosure, the term "server" should be understood as a point of service that provides processing, database, and communication facilities. By way of example and not limitation, the term "server" can refer to a single physical processor with associated communication, data storage, and database facilities, or it can refer to a complex of a network or cluster of processors and associated network and storage devices, as well as the operating software and one or more database systems and application software that support the services provided by the server. A cloud server is an example.

[0047] For the purposes of this disclosure, "network" should be understood to mean a network that couples devices to enable the exchange of communications, such as between server and client devices or other types of devices, including, for example, between wireless devices coupled via a wireless network. A network may also include, for example, mass storage such as Network Attached Storage (NAS), Storage Area Network (SAN), Content Delivery Network (CDN), or other forms of computer or machine-readable media. A network may include the Internet, one or more Local Area Networks (LANs), one or more Wide Area Networks (WANs), wired connections, wireless connections, cellular connections, or any combination thereof. Similarly, subnetworks that may employ different architectures or conform to or be compatible with different protocols may interoperate within a larger network.

[0048] For the purposes of this disclosure, "wireless network" should be understood as coupling client devices to a network. Wireless networks can employ standalone self-organizing networks, mesh networks, wireless LAN (WLAN) networks, cellular networks, etc. Wireless networks can also employ various network access technologies, including Wi-Fi, Long Term Evolution (LTE), WLAN, Wireless Router (WR) networks, or second-, third-, fourth-, or fifth-generation (2G, 3G, 4G, or 5G) cellular technologies, Bluetooth, 802.11b / g / n, etc. For example, network access technologies enable wide-area coverage of devices (such as client devices with varying degrees of mobility).

[0049] In short, wireless networks can include almost any type of wireless communication mechanism through which signals can be transmitted between devices such as client devices or computing devices, between networks, or within a network.

[0050] Computing devices may be able to send or receive signals (such as via wired or wireless networks), or may be able to process or store signals (such as in memory as physical memory), and therefore may operate as servers. Thus, devices capable of operating as servers, for example, may include dedicated rack servers, desktop computers, laptop computers, set-top boxes, integrated devices combining various features (such as two or more features of the aforementioned devices), etc.

[0051] For the purposes of this disclosure, client (or consumer or user) devices may include computing devices capable of transmitting or receiving signals (such as via wired or wireless networks). Client devices may include, for example, desktop computers or portable devices such as cellular phones, smartphones, display pagers, radio frequency (RF) devices, infrared (IR) devices, near field communication (NFC) devices, personal digital assistants (PDAs), handheld computers, tablet computers, tablet phones, laptop computers, set-top boxes, wearable computers, smartwatches, integrated or distributed devices combining various features (such as those of the aforementioned devices), etc.

[0052] Client devices can vary in terms of capabilities or features. The subject matter claimed is intended to cover a wide range of possible variations, such as web-enabled client devices or the aforementioned devices, which may include, for example, a high-resolution screen (e.g., HD or 4K), one or more physical or virtual keyboards, mass storage, one or more accelerometers, one or more gyroscopes, Global Positioning System (GPS) or other location identification capabilities, or a display with a high degree of functionality (such as a touch-sensitive color 2D or 3D display).

[0053] Certain embodiments will now be described in more detail with reference to the accompanying drawings. Generally, reference is made to... Figure 1The present disclosure illustrates a system 100 according to some embodiments thereof. Figure 1 The components of a general environment in which the systems and methods discussed herein can be practiced are shown. It is not necessary for all components to practice this disclosure, and variations in the arrangement and type of components can be made without departing from the spirit or scope of this disclosure. As shown, Figure 1 System 100 includes a local area network (“LAN”) / wide area network (“WAN”) 105, a wireless network 110, mobile devices (client devices) 102-104, and a client device 101. Figure 1 Additionally, it includes various servers, such as content server 106 and application (or “App”) server 108.

[0054] Some embodiments of mobile devices 102-104 may include virtually any portable computing device capable of receiving and sending messages over a network (such as network 105, wireless network 110, etc.). Mobile devices 102-104 may also be generally described as client devices configured as portable. Thus, as discussed above, mobile devices 102-104 may include virtually any portable computing device capable of connecting to another computing device and receiving information.

[0055] Mobile devices 102-104 may also include at least one client application configured to receive content from another computing device. In some embodiments, mobile devices 102-104 may also communicate with non-mobile client devices such as client device 101. In some embodiments, such communication may include sending and / or receiving messages, creating and uploading documents, searching, viewing and / or sharing memes, photos, digital images, audio clips, video clips, or any of a variety of other forms of communication.

[0056] Client devices 101-104 may be able to send or receive signals (such as via wired or wireless networks), or may be able to process or store signals (such as in memory as physical memory), and thus may operate as a server.

[0057] In some embodiments, wireless network 110 is configured to couple mobile devices 102-104 and their components to network 105. Wireless network 110 may include any of a variety of wireless subnetworks, which may also be overlaid with independent self-organizing networks, to provide infrastructure-oriented connectivity to mobile devices 102-104.

[0058] In some embodiments, network 105 is configured to couple content server 106, application server 108, etc., to other computing devices including client device 101, and to mobile devices 102-104 via wireless network 110. Network 105 is enabled to use any form of computer-readable medium or network to transmit information from one electronic device to another.

[0059] In some embodiments, content server 106 may include a device configured to provide content of any type or form to another device via a network. Devices that can operate as content server 106 include personal computers, desktop computers, multiprocessor systems, microprocessor-based or programmable consumer electronics, network PCs, servers, etc. In some embodiments, content server 106 may also provide a variety of services, including but not limited to email services, instant messaging (IM) services, streaming and / or downloading media services, search services, photo services, web services, social networking services, news services, third-party services, audio services, video services, SMS services, MMS services, FTP services, Voice over IP (VoIP) services, etc. Such services, such as email services and email platforms, may be provided via message server 120.

[0060] In some embodiments, users are able to access services provided by servers 106 and 108. This, in a non-limiting example, may include authentication servers, search servers, email servers, social networking service servers, SMS servers, IM servers, MMS servers, exchange servers, photo sharing service servers, and travel service servers, using their various devices 101-104 via network 105.

[0061] In some embodiments, the application server 108 may store various types of applications and application-related information, including application data and user profile information (e.g., information that identifies generation and / or observation associated with a user).

[0062] In some embodiments, content server 106 and app server 108 may store various types of data relating to the content and services they respectively provide, observe, identify, determine, generate, modify, retrieve, and / or collect. Such data may be stored in an associated content database 107, as discussed in more detail below.

[0063] In some embodiments, as discussed herein, servers 106 and / or 108 may be implemented as cloud servers or configured to host cloud services.

[0064] In some embodiments, network 105 is also coupled / connected to a Trusted Search Server (TSS), which can be used to render content according to the embodiments discussed herein. Embodiments exist in which TSS functionality can be implemented within servers 106 and 108.

[0065] Moreover, despite Figure 1 Servers 106 and 108 are illustrated as individual computing devices, but this disclosure is not limited thereto. For example, one or more functions of servers 106 and 108 may be distributed across one or more different computing devices. Furthermore, in some embodiments, servers 106 and 108 may be integrated into a single computing device without departing from the scope of this disclosure.

[0066] In addition, although Figure 1 The embodiments shown depict only servers 106 and 108, but they should not be construed as limiting, as they may include any type and number of servers.

[0067] Go to Figure 2 Computer system 210 is described above regarding Figure 1 Non-limiting example embodiments of the system 100 discussed.

[0068] Figure 2 The diagram illustrates what enables or allows operation. Figure 1 The computer system 210 of an embodiment of system 100 is discussed below. In some embodiments, computer system 210 may include and / or operate and / or process computer-executable code of one or more of the program logic, software modules, and / or systems mentioned above. Additionally, in some embodiments, computer system 210 may operate and / or display information within one or more graphical user interfaces. In some embodiments, computer system 210 may include a cloud server and / or may be coupled to one or more cloud-based server systems.

[0069] In some embodiments, system 210 may include at least one computing device 230, which includes at least one processor 232. In some embodiments, the at least one processor 232 may include a processor residing in or coupled to one or more server platforms. In some embodiments, system 210 may include a network interface 235a and an application interface 235b coupled to the at least one processor 232 capable of processing at least one operating system 234. Additionally, in some embodiments, the interfaces 235a, 235b coupled to the at least one processor 232 may be configured to process one or more software modules 238 (e.g., enterprise applications). In some embodiments, software module 238 may include server-based software and may be operable to host at least one user account and / or at least one client account, and to transfer data between one or more of these accounts using the at least one processor 232.

[0070] Considering the above embodiments, it should be understood that some embodiments may employ various computer-implemented operations involving data stored in a computer system. Furthermore, the database and model described throughout the text can store analytical models and other data on and coupled to a computer-readable storage medium within system 210. Additionally, the above-described applications of the system can be stored on and coupled to a non-transitory computer-readable storage medium within system 210.

[0071] In some embodiments, system 210 may include at least one non-transitory computer-readable medium 236 coupled to at least one data source 237a and / or at least one data storage device 237b and / or at least one input / output device 237c. In some embodiments, the disclosed systems and methods may be implemented as computer-readable code on computer-readable medium 236.

[0072] In some embodiments, computer-readable medium 236 may be any data storage device capable of storing data that can then be read by a computer system (such as system 210).

[0073] In some embodiments, the computer-readable medium 236 may be any physical or material medium that can be used to tangibly store desired information or data or instructions and that can be accessed by a computer or processor 232. In some embodiments, at least one of the software modules 238 may be configured within the system to output data to at least one user 231 via at least one graphical user interface rendered on at least one digital display.

[0074] In some embodiments, the non-transitory computer-readable medium 236 may be distributed over a conventional computer network via a network interface 235a, wherein the system implemented by computer-readable code may be stored and executed in a distributed manner. For example, in some embodiments, one or more components of system 210 may be coupled via a local area network (“LAN”) 239a and / or an internet-coupled network 239b (e.g., a wireless internet) to send and / or receive data. In some other embodiments, networks 239a, 239b may include a wide area network (“WAN”), a direct connection (e.g., via a universal serial bus port), or other forms of computer-readable medium 236, or any combination thereof.

[0075] In some embodiments, components of networks 239a, 239b may include any number of user devices, such as personal computers coupled via LAN 239a, including, for example, desktop computers and / or laptop computers, or any stationary, generally non-mobile Internet device. For example, some embodiments include a personal computer 240a coupled via LAN 239a, which can be configured for any type of user, including an administrator. Other embodiments may include a personal computer coupled via network 239b. In some additional embodiments, one or more components of system 210 may be coupled via an Internet network (e.g., such as network 239b) to send or receive data. For example, some embodiments include at least one user 231 who is wirelessly coupled and accesses one or more software modules of a system including at least one enterprise application 238 via input and output (“I / O”) device 237c. In some other embodiments, system 210 may enable at least one user 231 to be coupled via LAN 239a to access enterprise application 238 via I / O device 237c. In some embodiments, user 231 may include user 231a coupled to system 210 using a desktop computer and / or laptop computer coupled via Internet 239b or any fixed, generally non-mobile Internet device. In some embodiments, user 231 may include mobile user 231b coupled to system 210. In some embodiments, user 231b may use any mobile computing device 231c to wirelessly couple to system 210, including but not limited to personal digital assistants, and / or cellular phones, mobile phones or smartphones, and / or pagers, and / or digital tablets, and / or fixed or mobile Internet devices.

[0076] Figure 3 This is a schematic diagram illustrating a client device, showing an example embodiment of a client device that can be used within this disclosure. Client device 300 may include a plurality of... Figure 3The components shown may be more or less than the components shown. However, the components shown are sufficient to disclose illustrative embodiments for implementing this disclosure. Client device 300 may represent, for example, the components described above. Figure 1-2 The client devices discussed.

[0077] like Figure 3 As shown, in some embodiments, client device 300 includes a processing unit (CPU) 322 that communicates with mass storage 330 via bus 324. In some embodiments, client device 300 also includes a power supply 326, one or more network interfaces 350, an audio interface 352, a display 354, a keypad 356, a illuminator 358, an input / output interface 360, a haptic interface 362, an optional global positioning system (GPS) receiver 364, and a camera or other optical, thermal, or electromagnetic sensor 366. As those skilled in the art will understand, device 300 may include one or more cameras / sensors 366. Power supply 326 provides power to client device 300.

[0078] Client device 300 may optionally communicate with a base station (not shown) or directly with another computing device. Network interface 350 is sometimes referred to as a transceiver, transceiver device, or network interface card (NIC).

[0079] In some embodiments, the audio interface 352 is arranged to generate and receive audio signals, such as the sound of human speech. The display 354 may be a liquid crystal display (LCD), a gas plasma display, a light-emitting diode (LED), or any other type of display used with a computing device. The display 354 may also include a touch-sensitive screen arranged to receive input from an object, such as a stylus or a finger from a human hand.

[0080] The keypad 356 may include any input device arranged to receive input from the user. The illuminator 358 may provide status indication and / or provide light.

[0081] In some embodiments, the client device 300 further includes an input / output interface 360 ​​for communicating with external devices. The input / output interface 360 ​​may utilize one or more communication technologies, such as USB, infrared, or Bluetooth. TM In some embodiments, the haptic interface 362 is arranged to provide haptic feedback to a user of a client device.

[0082] An optional GPS transceiver 364 can determine the physical coordinates of the client device 300 on the Earth's surface, typically outputting the location as latitude and longitude values. The GPS transceiver 364 can also employ other geolocation mechanisms, including but not limited to triangulation, assisted GPS (AGPS), E-OTD, CI, SAI, ETA, BSS, etc., to further determine the physical location of the client device 300 on the Earth's surface. However, in some embodiments, the client device may provide additional information that can be used to determine the device's physical location through other components, including, for example, a MAC address, an Internet Protocol (IP) address, etc.

[0083] In some embodiments, mass storage 330 includes RAM 332, ROM 334, and other storage components. Mass storage 330 illustrates another example of a computer storage medium for storing information such as computer-readable instructions, data structures, program modules, or other data. Mass storage 330 stores a Basic Input / Output System (“BIOS”) 340 for controlling the low-level operation of client device 300. Mass storage also stores an operating system 341 for controlling the operation of client device 300.

[0084] In some embodiments, memory 330 also includes one or more data repositories that client device 300 can utilize to store application 342 and / or other information or data, among other things. For example, data repositories may be employed to store information describing various capabilities of client device 300. This information can then be provided to another device based on any of various events, including being sent as part of a header (e.g., an index file for an HLS stream) during communication, being sent upon request, etc. At least a portion of the capability information may also be stored on a disk drive or other storage medium (not shown) within client device 300.

[0085] In some embodiments, application 342 may include computer-executable instructions that, when executed by client device 300, transmit, receive, and / or otherwise process audio, video, and images, and enable remote communication with a server and / or another user on another client device. In some embodiments, application 342 may also include a search client 345 configured to send, receive, and / or otherwise process search queries and / or search results.

[0086] The components of a general architecture used in some embodiments have been described, and the general operation of the components with respect to some embodiments will now be described below.

[0087] Figure 4 This is a block diagram illustrating components of some embodiments. Figure 4 This includes a UI engine 400, a network 415, and a database 420. The user interface (UI) engine 400 can be a dedicated machine or processor and can be hosted by a cloud server (e.g., a cloud web service server), a messaging server, an application server, a content server, a social networking server, a web server, a search server, a content provider, a third-party server, a user's computing device, or any combination thereof.

[0088] According to some embodiments, the UI engine 400 can be implemented as a standalone application that executes on a server and / or user device (e.g., on a cloud server and / or user device or on-prem on local storage). In some embodiments, the UI engine 400 can be used as an application installed on a device; and in some embodiments, such an application can be a web-based application accessed by the device over a network.

[0089] Database 420 can be any type of database or storage, and can be connected to a content server on a network (e.g., a cloud server, content server, search server, or application server) or a user's device (e.g., the one mentioned above). Figure 1-3 The database 420 is associated with the client devices discussed herein. Database 420 includes datasets of data and metadata associated with local and / or network information related to users, services, applications, content, etc. Such information can be stored and indexed independently and / or as linked or associated datasets within database 420. As discussed above, it should be understood that, without departing from the scope of this disclosure, the data (and metadata) in database 420 can be any type of information and data, whether known or to be known.

[0090] According to some embodiments, database 420 may store data and metadata associated with services and items, users, operations, tasks, assets, files, projects, versions, synchronization events, schedules, images, videos, text, messages, products, etc., from a wide variety of media and / or service providers and / or platforms.

[0091] According to some embodiments, database 420 may store user data, such as user data. According to some embodiments, the stored user data may include, but is not limited to, information associated with a user profile, user interests, user behavior information, user attributes, user preferences or settings, user demographic information, user location information, user biographical information, or some combination thereof.

[0092] In some embodiments, user data may also include user device information, including but not limited to device identification information, device capability information, voice / data carrier information, applications installed or capable of being installed or executed on such devices, and / or any one or a combination thereof. It should be understood that, without departing from the scope of this disclosure, the data (and metadata) in database 420 may be any type of information relating to users, assets, locations, jobs, operations, content, devices, applications, service providers, or content providers, whether known or to be known.

[0093] As discussed above, refer to Figure 1-2 Network 415 can be any type of network, such as, but not limited to, wireless networks, local area networks (LANs), wide area networks (WANs), the Internet, or combinations thereof. Network 415 facilitates the connection between the UI engine 400 and the database 420 storing resources. In fact, as... Figure 4 As shown, the UI engine 400 and the database 420 can be directly connected via any known or future connection and / or method that enables such communication between devices and resources.

[0094] The combination of a main processor, server, or device, including hardware programmed according to the specific functions described herein, is conveniently referred to as UI engine 400, and includes asset data module 402, filtering module 404, compilation module 406, and display module 408. It should be understood that the engines and modules discussed herein are not exhaustive, as additional or fewer engines and / or modules (or sub-modules) may be applied to embodiments of the systems and methods discussed. The operation, configuration, and function of each module, and their role within embodiments of this disclosure, will be discussed below.

[0095] Now go to Figure 5-10 This document discusses examples of how a public user interface can display and manipulate asset data. According to some embodiments, asset data may correspond to an asset (e.g., a tool referred to as a physical asset), location, task, operation, place, etc., or some combination thereof. In some embodiments, the asset data discussed herein refers to data that is anomaly-related to a physical asset at a location.

[0096] In some embodiments, as described below Figure 5-11The disclosed UI discussed herein can display asset data in any form of electronic or digital information; however, it should not be construed as restrictive, as any type of digital information, whether known or to be known, can be displayed within the UI without departing from the scope of this application. For example, the UI can display asset data as any type of image, text, video, tile, multimedia, RSS data, graphics, diagrams, icons, charts, augmented reality (AR) depictions, virtual reality (VR) depictions, messages, hyperlinks (or URLs), or any other type of interactive data or interface object detailing the operation of the asset at a location, or some combination thereof.

[0097] Figure 5 The UI 500 is illustrated, providing an interactive display of interface objects and sections that convey a framework for understanding and controlling specific operations (both current and future operations). UI 500 depicts object 502, which provides indications of "information" corresponding to specific operations or measurements that have occurred—examples of past operation measurements are depicted in section 508. This list 508 can be sorted based on criteria (e.g., recent, by date, etc.) to rank or filter operations. Item 518 allows only operations awaiting viewing to be displayed within list 508 (e.g., "unread" asset data).

[0098] Item 516 shows the time when the last update occurred. This last update may correspond to the last time the sorting occurred, the last time the operation was completed and its data was received, stored, compiled, and / or depicted in the UI, or some combination thereof.

[0099] In some embodiments, the selection of items within list 508 can display additional information within the UI. This information can be displayed in dedicated sections—items 504 and 506. These sections respectively display asset functionalities for a specific task selected from list 508. In some embodiments, items 504 and 506 can illustrate current or past measurements or attributes of a specific asset operated at a specific location associated with a specific operation.

[0100] In some embodiments, items 504 and 506 can be selected and moved to different locations within the UI. In some embodiments, items 504 and 506 can be moved to different windows and displayed in windows adjacent to UI 500. In some embodiments, items 504 and 506 can be displayed as separate tabs within the UI, where list 508 is one tab, and other interactive tabs correspond to items 506 and 508 respectively.

[0101] Items 510, 512, and 514 provide functionality for further searching, filtering, and sorting the tasks listed in list 508. The searching, filtering, and / or sorting disclosed herein can be based on a combination of interactions with items 510-514, each individual item, or some combination thereof.

[0102] Project 510 (also depicted in) Figure 7 (In the middle) enables the search to be performed on data of a certain type within the operation (e.g., type of exception—e.g., related exception, irrelevant exception, or non-exception). Item 510 enables the search to be created and executed, allowing tasks within list 508 to be identified and displayed. This will produce a modified list 508 such that only tasks with the data type identified in item 510 will be displayed within list 508.

[0103] Item 512 enables the searching of specific tasks within a selected timeframe in a manner similar to that discussed above with respect to Item 510. For example, such timeframes may include, but are not limited to, any time, the past 24 hours, today, this week, and this month. In some embodiments, timeframes may be dynamically determined based on operational data or analysis of previously performed similar types of operations, assets, or locations—for example, a specific type of asset generates accurate data every 5 hours; this 5-hour period may be added as a selectable object to the menu of Item 512 to recommend it to the user when viewing another asset of the same type. Item 512 is also depicted in… Figure 8 In addition, it enables the display of a list of modifications based on the selected and applied criteria.

[0104] Item 514 enables the searching of feedback of a certain type in a manner similar to that discussed above regarding Items 510-512—for example, also as Figure 9 As shown, specific tasks may have no feedback, be related to anomalies, be unrelated to anomalies, or be non-anomalies.

[0105] For example, when viewing task data, or based on the following: Figure 11 In the specific application of machine learning analysis (e.g., artificial intelligence (AI) models) discussed in process 1100, if a data item initially classified as anomalous is determined not to actually be anomalous, then that data can be modified and stored along with data indicating such feedback. When "Non-anomalous" is selected in item 514, list 508 can be modified based on the feedback received to display this task.

[0106] Figure 6The illustration shows an example embodiment of UI 600 where, when task 602 is selected from list 508, its data can be visually displayed within section 604. In a similar manner to that discussed above regarding items 504 and 506, section 604 can be a dedicated portion of UI 600. Such a section could, for example, display asset functionalities for a specific task selected from list 508. In some embodiments, section 604 can illustrate current or past measurements or attributes of a specific asset operated at a specific location associated with a specific operation.

[0107] In some embodiments, portion 604 can be selected and moved to different locations within the UI. In some embodiments, portion 604 can be moved to different windows and displayed in a window adjacent to UI 600. In some embodiments, portion 604 can be displayed as a separate tab within the UI, where list 508 is one tab and another interactive tab corresponds to portion 604.

[0108] Now go to Figure 10 This describes a UI 1000 that enables navigation of a set of content / information via a navigation control 1002. In some embodiments, the control 1002 may correspond to a specific event, action, task, or operation of an asset, or a combination thereof. In some embodiments, such as Figure 10 As shown in the example embodiment of UI 1000, control 1002 can correspond to the hierarchy of locations.

[0109] Navigation triggered by selection from control 1002 generates list 1004, which displays asset data for a specific task based on the selection—as discussed above (and as depicted in UI 1000, for example, a "feedback" column), which can be filtered, for example, in the manner discussed above with respect to items 510-514. For example, in some embodiments, list 1004 can be updated accordingly to show asset data only from a specific location (e.g., anomalies).

[0110] It should be understood that although UI 1000 only displays feedback options, it should not be interpreted as restrictive, because any other type of filtering options available in UI 500 or UI 600 are available in UI 1000, and vice versa.

[0111] In some embodiments, a user can navigate to another page using navigation control 1002. In some embodiments, control 1002 can check whether a new anomaly has been detected. Such checks or monitoring can occur periodically. In some embodiments, if a new anomaly is detected, control 1002 can automatically update the list without user input. As discussed above, such updates can be indicated in a manner similar to item 516 in UI 500.

[0112] Now go to Figure 11 Process 1100 details non-limiting embodiments of an interactive user interface (UI) for automatically generating and dynamically updating, according to some embodiments, the UI including digital information related to multiple processes and operations. The UI provides consistent functionality across platforms, devices, and / or services used to view the UI and / or the interface objects (e.g., tiles) included therein and / or to interact with the UI and / or the interface objects (e.g., tiles) included therein. The UI provides dynamic mechanisms for controlling assets, as well as mechanisms for comparing data of different assets (thereby allowing some assets to be manipulated). The UI enables the detection and contextualized visualization of operational data of assets and / or locations in a distributed SCADA system within a cloud-connected environment.

[0113] According to some embodiments of process 1100, step 1102 is executed by the asset data module 402 of UI engine 400; steps 1104 and 1110 are executed by compilation module 406; steps 1106-1108 are executed by filtering module 404; and steps 1112-1116 are executed by display module 408.

[0114] Process 1100 begins at step 1102, in which operational or asset data corresponding to a set of assets associated with at least one operation at one or more locations is received. As discussed above, the asset data corresponds to data collected by instruments, tools, or other equipment related to the operation of an asset at a location.

[0115] For the purposes of this discussion, assets will refer to physical tools or machinery that operate at a location. However, it should not be construed as restrictive, as assets can also be computerized programs, applications, or other electronic devices that operate computer instructions on such physical equipment.

[0116] For the purposes of this discussion, asset data will refer to data collected in connection with the operation of one or more physical assets at one or more locations over a period of time, such that the data indicates the occurrence of at least one anomaly. Therefore, in some embodiments, asset data is received in step 1102 when a threshold of the number of anomalies is detected in the asset. Upon such detection, the anomalous asset data is compiled and received by engine 400.

[0117] Step 1102 also involves storing the asset data in a data repository associated with engine 400. For example, database 402, as discussed above. Storage may involve storage in a cloud-based or cloud-hosted system. According to some embodiments, such storage may involve any known or to be known storage technology, process, or algorithm, but is not limited to, storage using lookup tables (LUTs), hash trees, blockchains, indexing, etc., or some combination thereof.

[0118] According to some embodiments, asset data is received and stored in a cloud-based cache (also known as a web-based cache), making it accessible to engine 400. In such embodiments, as discussed herein with respect to process 1100, when an anomaly is detected at a specific location, anomalous data is automatically captured and sent to the web cache for further processing and display by engine 400.

[0119] In step 1104, a UI is generated, which displays asset data for the specific operation received. In some embodiments, the asset information displayed within the UI can be configured to be associated with the SCADA navigation context. As discussed above, in Figure 5 , Figure 6 and Figure 10 The figures illustrate some non-limiting example embodiments of such a display.

[0120] According to some embodiments, asset data can be displayed as selectable and / or in any type of known or to be known form, type or format of interactive asset information, but not limited to, diagrams, tiles, A / R, V / R, etc.

[0121] According to some embodiments, engine 400 may perform analysis on the data received in step 1102 so as to display at least a portion of it within the UI generated in step 1104. According to some embodiments, such analysis may involve any type of known or to be known computational analysis techniques, including but not limited to vector analysis, data mining, computer vision, machine learning, neural networks, artificial intelligence, etc., or some combination thereof.

[0122] Proceed to step 1106, where the UI is as follows Figure 5 , Figure 6 and Figure 10 When displayed as shown, it can receive input instructions including filtering, sorting, or searching specific information items within the received and displayed asset information.

[0123] In some embodiments, input may be provided by the user in response to viewing the displayed asset information and, for example, as described above regarding... Figure 5 and Figure 7-9 The filter menus described in items 510-514 are provided for interactive purposes.

[0124] In some embodiments, the input may be computer-generated. For example, while data is being displayed, a computer script, program, or application may execute at a location to check for anomalies according to certain criteria. This could be part of maintenance procedures running at the site or part of a comprehensive audit of asset operations.

[0125] In some embodiments, the input may be the result of a machine learning component of engine 400. As discussed below, engine 400 can be trained to understand which types of anomalies the user is most interested in as data is displayed and filtered (which causes modifications to the specific type and form of data being displayed). Therefore, when new anomalous data is detected and displayed, engine 400 can automatically filter the display to show the anomalous data that is of most interest to the user or that is most relevant to ensuring the operational integrity of the assets at the location.

[0126] As a non-limiting example, the input used to filter the content / information displayed on the UI can be related to the above regarding... Figure 5 , Figure 7 , Figure 8 , Figure 9 and Figure 10 The discussion relates to interactive filtering components. For example, as discussed above, input can request sorted / filtered information about specific anomalies that have a specific type of anomaly (e.g., via item 510), occurred within / during a specific time frame, and / or have received feedback (e.g., via item 514), or some combination thereof. In another example, as mentioned above regarding... Figure 10 As discussed in control 1002, the input can be a navigation request for locating a specific anomaly at a specific location.

[0127] In step 1108, the displayed and / or selected (via input) asset data is analyzed based on the filtering input from step 1106. In some embodiments, such filtering may involve generating a search query that includes information related to the filtering input, and then performing a search of stored asset data (at database 420 and / or at a network cache). This search can return a reduced version of the displayed data based on the filtering input.

[0128] According to some embodiments, the analysis and search in step 1108 can be performed by engine 400 using any type of known or to be known computational analysis techniques, including but not limited to vector analysis, data mining, computer vision, machine learning, neural networks, artificial intelligence, or some combination thereof.

[0129] In step 1110, the UI is modified to include the filtering results from steps 1106-1108; and, as a result, the modified UI is displayed. Step 1112. In some embodiments, the asset information displayed within the UI can be configured to be associated with the SCADA navigation context.

[0130] According to some embodiments, the modified UI may involve changing how data is displayed, reducing or increasing the amount of data displayed, or some combination thereof.

[0131] For example, the filtered input from step 1106 can request only exceptions for which a specific type of feedback has been received. Therefore, the list of information can be narrowed down (e.g., Figure 8 (List 508 in the diagram). However, in some embodiments, additional data illustrating components of the remaining list data can now be displayed. For example, new UI sections can be displayed (e.g., Figure 5 Project 504 and / or 506, or Figure 6 (Part 604 in the document). This modifies the look and feel of UI 500, and now displays additional data that was not previously shown in it.

[0132] In some embodiments, input can also alter how data is displayed. For example, an input request can request data to be displayed in a format different from how it was originally displayed. This can cause a modification to the data structure of the displayed data, changing it from one type of data structure format to another, thereby altering not only how it is rendered, but also how the UI is rendered and how the engine 400 facilitates such rendering.

[0133] For example, if the data is initially displayed as a line graph, but the user wants the information to be virtually displayed as an overlay captured in the real world, the line graph can be changed to an A / R view, which can be achieved via the UI. In such an embodiment, engine 400 can utilize the device's camera capabilities to modify the UI display.

[0134] In some embodiments, such as those described above regarding items 510-514 and Figure 5 and Figure 7-9 The UI modifications discussed may also include, or alternatively include, modifications to the filter menu, through which asset data can be sorted, searched, or filtered.

[0135] When the modified UI is displayed in step 1112, information relating to how the UI was modified (e.g., from step 1110) and why it was modified (e.g., from the filtering and analysis of steps 1106-1108) can be fed back to the compilation module 406 of engine 400 via the feedback loop described between steps 1112 and 1104. As discussed above, this enables engine 400 to more accurately analyze (e.g., understand by being trained on feedback data) and display data of a specific type or form based on user viewing and / or interaction behavior. In some embodiments, such additional data can enable engine 400 to more accurately request, retrieve, collect, and / or monitor future anomalies from similar assets or from specific locations.

[0136] Process 1100 now proceeds to step 1114, in which the UI facilitates a network connection with the distributed system's electronics via the displayed UI. For example... Figure 11 As described, such a connection can be established when the UI is displayed (according to step 1104) or in response to a modified UI (according to step 1112).

[0137] As a result of the connection established in step 1114, the UI can provide the user with computerized control over a specific asset or operation occurring at a location.

[0138] As a non-restrictive example, the user is presented from Figure 5 The UI 500 shows the asset data. The user selects item 602 from list 508, and its data is displayed in section 604 (e.g., ...). Figure 6 (As shown). The user then provides input for the "Related Exceptions" (item 510) that requests data from the past 24 hours (item 512) and feedback indicating "Related Exceptions" (item 514). The user also provides a navigation request for data from a specific location in control 1002.

[0139] Based on this example, the results of anomalous data are thus narrowed down according to the requested criteria, resulting in a modified UI being displayed. For example, a user could view anomalous data on physical assets at workplaces in Sydney, Australia, collected over the past 24 hours.

[0140] As discussed in this article, the UI enables direct connection to this remote workplace, providing users with control over that specific asset. Users can, for example, perform maintenance on the asset to remedy anomalies indicated by filtered data.

[0141] According to some embodiments, as a result of step 1116, data corresponding to how the asset is controlled can be collected and fed back to steps 1102, 1104, or 1112. Information related to how a specific asset is controlled in response to a detected anomaly can drive how future anomalous data is requested, collected, retrieved, and / or ignored (e.g., step 1102), and can also affect how and when it is displayed (e.g., steps 1104 and / or 1112).

[0142] Therefore, as a result of the execution of steps 1102-1116, the UI (e.g., UI 500, 600, and 1000, for example) provides functionality across platforms, devices, and / or services used to view the UI and / or the interface objects included therein and / or interact with the UI and / or the interface objects included therein. The UI provides dynamic mechanisms for controlling assets, as well as mechanisms for comparing data from different assets (therefore, some assets can subsequently be manipulated). The UI enables the detection and contextualized visualization of operational data for assets and / or locations in a distributed Supervisory Control and Data Acquisition (SCADA) system within a cloud-connected environment.

[0143] For the purposes of this disclosure, a module is a software, hardware, or firmware (or a combination thereof) system, process, or function, or a component thereof, that performs or facilitates the processes, features, and / or functions (with or without human interaction or enhancements) described herein. A module may include submodules. The software components of a module may be stored on a computer-readable medium for execution by a processor. A module may be integrated into one or more servers, or loaded and executed by one or more servers. One or more modules may be grouped into an engine or application.

[0144] For the purposes of this disclosure, the terms “user,” “subscriber,” “consumer,” or “customer” should be understood to mean a user of one or more applications as described herein and / or a consumer of data supplied by a data provider. By way of example and not limitation, the terms “user” or “subscriber” may refer to a person who receives data supplied by a data or service provider over the Internet in a browser session, or may refer to an automated software application that receives, stores, or processes data.

[0145] Those skilled in the art will recognize that the methods and systems disclosed herein can be implemented in many ways and are therefore not limited to the foregoing exemplary embodiments and examples. In other words, functional elements and individual functions performed by one or more components in various combinations of hardware and software or firmware can be distributed within a software application at either the client level or the server level, or both. In this regard, any number of features of the different embodiments described herein can be combined into one or more embodiments, and alternative embodiments having fewer or more features than all those described herein are possible.

[0146] Functionality can also be distributed, wholly or partially, across multiple components in ways now known or to be known. Therefore, a wide variety of software / hardware / firmware combinations are possible in implementing the functions, features, interfaces, and preferences described herein. Furthermore, the scope of this disclosure covers conventionally known methods for performing the described features, functions, and interfaces, as well as those variations and modifications that may be made to the hardware or software or firmware components described herein, as will be understood by those skilled in the art now and in the future.

[0147] Furthermore, embodiments of the methods presented and described as flowcharts in this disclosure are provided by way of example to provide a more complete understanding of the technology. The disclosed methods are not limited to the operations and logical flows presented herein. Alternative embodiments are contemplated, wherein the order of various operations is altered, and wherein sub-operations described as part of a larger operation are performed independently.

[0148] While various embodiments have been described for the purposes of this disclosure, it should not be construed that such embodiments limit the teachings of this disclosure to those embodiments. Various changes and modifications can be made to the above elements and operations to obtain results within the scope of the systems and processes still described in this disclosure.

Claims

1. A computing device for displaying a user interface (UI), comprising: One or more processors; A non-transitory computer-readable storage medium storing computer-executable instructions therein, which, when executed by the one or more processors, cause the one or more processors to perform actions that display a user interface (UI), the actions including: Electronic data related to the operation of a physical asset at a location is received via a network, the electronic data representing at least one detected anomaly of the asset during a time period and received when a threshold of the number of anomalies detected on the physical asset is met. The UI is created in response to receiving electronic data indicating an anomaly of the at least one detection. The created UI includes functionality for displaying at least a portion of the received electronic data as interactive digital content based on analysis of the received electronic data. The UI is displayed on the screen of the first client device via the network; Receive a request from the first client device for electronic data to be displayed for a specific anomaly filtering; The UI is modified by automatically changing the amount and type of interactive digital content displayed within it in response to a received filtering request for the displayed electronic data; The network receives input from a second client device regarding a portion of altered digital content, the portion corresponding to an anomaly in the asset. In response to the display or modification of the UI, an electronic connection is electronically established between the first client device and a device associated with the asset and the location via the network, the established connection including functionality that enables the first client device to control the asset via the network through the modified UI; The modified UI receives control commands for the asset from the first client device via the network, the control commands corresponding to remedies for anomalies of the asset; Control data, including the control commands, is stored in the non-transitory computer-readable storage memory; and By using the control data as part of the basis for the analysis of future electronic data, one or more of the following can be modified: how and / or when future anomalous data is requested, collected, retrieved, ignored, and displayed. The control data is associated with the anomalousness of the asset, and the future electronic data is associated with the operation of the physical asset at the location.

2. The computing device of claim 1, further comprising: The electronic data is stored in a cloud-based network cache, wherein receiving the electronic data includes retrieving the electronic data from the cache.

3. The computing device of claim 1, wherein the control includes executing an application via the network through the UI, the application performing maintenance operations on the asset.

4. The computing device of claim 1, wherein the filtering request is in response to interaction with at least a portion of the interactive digital content.

5. The computing device of claim 1, further comprising: Analyze the electronic data of the assets; as well as The filtering request is automatically generated based on the analysis of the electronic data of the assets without requiring user input.

6. The computing device of claim 1, wherein the filtering request includes a set of criteria corresponding to the type of data included in the electronic data associated with the anomaly.

7. The computing device of claim 1, wherein the filtering request enables navigation of specific types of asset data related to multiple locations.

8. The computing device of claim 1, wherein the electronic connection is established when the UI is first displayed on the first client device.

9. The computing device of claim 1, further comprising: Collect information related to control over the assets.

10. The computing device of claim 9, further comprising: The second set of electronic data was received, at least in part, based on the information collected.

11. The computing device of claim 1, further comprising: Collect information related to the filtering request and the modification of the UI.

12. The computing device of claim 11, further comprising: Receive the second set of electronic data; as well as The UI is updated based on the second set of electronic data and the collected information.

13. The computing device of claim 1, further comprising: Analyze the received electronic data; as well as The type of display format of the received electronic data is determined based on the analysis of the electronic data, wherein the display of the electronic data within the UI is at least in part based on the determined type.

14. A method for displaying a user interface (UI), comprising: Electronic data relating to the operation of a physical asset at a location is received by a computing device via a network, the electronic data representing at least one detected anomaly of the asset during a time period and received when a threshold of the number of anomalies detected in the physical asset is met. The computing device creates a user interface (UI) in response to receiving electronic data representing an anomaly of the at least one detected event. The created UI includes functionality for displaying at least a portion of the received electronic data as interactive digital content based on analysis of the received electronic data. The computing device displays the UI on the display of the first client device via the network; The computing device receives a request from the first client device for electronic data to be displayed for a specific anomaly filtering. The computing device modifies the UI by automatically changing the quantity and type of interactive digital content displayed within the UI in response to receiving a filtering request for the displayed electronic data; The computing device receives input from a second client device via the network regarding a portion of modified digital content, the portion corresponding to an anomaly in the asset; The computing device, in response to the display or modification of the UI, electronically establishes an electronic connection between the first client device and a device associated with the asset and the location via the network, the electronic connection including functionality that enables the first client device to control the asset via the network through the modified UI; The modified UI receives control commands for the asset from the first client device via the network, the control commands corresponding to remedies for anomalies of the asset; Control data, including the control commands, is stored in the non-transitory computer-readable storage memory. as well as By using the control data as part of the basis for the analysis of future electronic data, one or more of the following can be modified: how and / or when future anomalous data is requested, collected, retrieved, ignored, and displayed. The control data is associated with the anomalousness of the asset, and the future electronic data is associated with the operation of the physical asset at the location.

15. The method of claim 14, further comprising: The electronic data is stored in a cloud-based network cache, wherein receiving the electronic data includes retrieving the electronic data from the cache.

16. The method of claim 14, further comprising: Collect information related to control of the assets; as well as The second set of electronic data was received, at least in part, based on the information collected.

17. The method of claim 14, further comprising: Collect information related to the filtering request and the modification of the UI; Receive the second set of electronic data; as well as The UI is updated based on the second set of electronic data and the collected information.

18. The method of claim 14, further comprising: Analyze the received electronic data; as well as The type of display format for the electronic data is determined based on the analysis, wherein the display of the electronic data within the UI is at least in part based on the determined type.

19. A non-transitory computer-readable storage medium tangibly encoded with computer-executable instructions, which, when executed by a processor associated with a computing device, perform a method comprising: Electronic data relating to the operation of a physical asset at a location is received by a computing device via a network, the electronic data representing at least one detected anomaly of the asset during a time period and received when a threshold of the number of anomalies detected in the physical asset is met. In response to receiving electronic data indicating an anomaly of the at least one detected event, a user interface (UI) is created, the created UI including functionality for displaying at least a portion of the received electronic data as interactive digital content based on analysis of the received electronic data; The UI is displayed on the screen of the first client device via the network; Receive a request from the first client device for electronic data to be displayed for a specific anomaly filtering; The UI is modified by automatically changing the amount and type of interactive digital content displayed within it in response to a received filtering request for the displayed electronic data; The network receives input from a second client device regarding a portion of altered digital content, the portion corresponding to an anomaly in the asset. In response to the display or modification of the UI, an electronic connection is electronically established between the first client device and a device associated with the asset and the location via the network, the established connection including functionality that enables the first client device to control the asset via the network through the modified UI; The modified UI receives control commands for the asset from the first client device via the network, the control commands corresponding to remedies for anomalies of the asset; Control data, including the control commands, is stored in the non-transitory computer-readable storage memory. as well as By using the control data as part of the basis for the analysis of future electronic data, one or more of the following can be modified: how and / or when future anomalous data is requested, collected, retrieved, ignored, and displayed. The control data is associated with the anomalousness of the asset, and the future electronic data is associated with the operation of the physical asset at the location.

20. The non-transitory computer-readable storage medium of claim 19, further comprising: The electronic data is stored in a cloud-based network cache, wherein receiving the electronic data includes retrieving the electronic data from the cache.

Images