# Patent

## Title
Remote industrial monitoring using a cloud infrastructure

## Abstract

A cloud-based infrastructure facilitates gathering, transmitting, and remote storage of control and automation data using an agent-based communication channel. The infrastructure collects the industrial data from an industrial enterprise and intelligently sorts and organizes the acquired data based on selected criteria. Message queues can be configured on the cloud platform to segregate the industrial data according to priority, data type, or other criteria. Behavior assemblies stored in customer-specific manifests on the cloud platform define customer-specific preferences for processing data stored in the respective message queues. Web-based tools can deliver automated notifications to an end user device based on analysis of the stored data, and allow the user to remotely view the stored data.

## Background
CROSS-REFERENCE TO RELATED APPLICATIONS
This application claims priority to U.S. Provisional Application Ser. No. 61/681,443, filed on Aug. 9, 2012, entitled “REMOTE INDUSTRIAL MONITORING USING A CLOUD INFRASTRUCTURE,” the entirety of which is incorporated by reference.


TECHNICAL FIELD
This disclosure relates generally to systems and methods that provide remote monitoring services for an industrial automation system over a cloud infrastructure
BACKGROUND
Industrial controllers and their associated I/O devices are central to the operation of modern automation systems. These controllers interact with field devices on the plant floor to control automated processes relating to such objectives as product manufacture, material handling, batch processing, supervisory control, and other such applications. Industrial controllers store and execute user-defined control programs to effect decision-making in connection with the controlled process. Such programs can include, but are not limited to, ladder logic, sequential function charts, function block diagrams, structured text, or other such programming structures.
Because of the large number of system variables that must be monitored and controlled in near real-time, industrial automation systems often generate vast amounts of near real-time data. In addition to production statistics, data relating to machine health, alarm statuses, operator feedback (e.g., manually entered reason codes associated with a downtime condition), electrical or mechanical load over time, and the like are often monitored, and in some cases recorded, on a continuous basis. This data is generated by the many industrial devices that can make up a given automation system, including the industrial controller and its associated I/O, telemetry devices for near real-time metering, motion control devices (e.g., drives for controlling the motors that make up a motion system), visualization applications, lot traceability systems (e.g., barcode tracking), etc. Moreover, since many industrial facilities operate on a 24-hour basis, their associated automation systems can generate a vast amount of potentially useful data at high rates. For an enterprise with multiple plant facilities, the amount of generated automation data further increases
The large quantity of data generated by modern automation systems makes it possible to apply a broad range of plant analytics to the automation systems and processes that make up an industrial enterprise or business. However, access to the industrial data is typically limited to applications and devices that share a common network with the industrial controllers that collect and generate the data. As such, plant personnel wishing to leverage the industrial data generated by their systems in another application (e.g., a reporting or analysis tool, notification system, visualization application, backup data storage, etc.) are required to maintain such applications on-site using local resources. Moreover, although a given industrial enterprise may comprise multiple plant facilities at geographically diverse locations (or multiple mobile systems having variable locations), the scope of such applications is limited only to data available on controllers residing on the same local network as the application.
The above-described deficiencies of today's industrial control and business systems are merely intended to provide an overview of some of the problems of conventional systems, and are not intended to be exhaustive. Other problems with conventional systems and corresponding benefits of the various non-limiting embodiments described herein may become further apparent upon review of the following description
SUMMARY
The following presents a simplified summary in order to provide a basic understanding of some aspects described herein. This summary is not an extensive overview nor is intended to identify key/critical elements or to delineate the scope of the various aspects described herein. Its sole purpose is to present some concepts in a simplified form as a prelude to the more detailed description that is presented later.
One or more embodiments of the present disclosure relate to deployment of cloud data storage farms for storing alarm, historical, and live automation data using an agent-based communication channel. To this end, a cloud-based infrastructure according to one or more embodiments described herein can facilitate gathering, transmitting, and remotely storing control and automation data and relating information. The infrastructure can collect the industrial data from data collectors in an industrial enterprise, including but not limited to SQL systems, data historians, data tables, or other such plant floor and/or business-level collectors. The cloud-based infrastructure can intelligently sort and organize the acquired data based on selected criteria (e.g., time of occurrence of a plant-floor event, priority, etc.). In order to transfer data from the plant floor to the cloud, the infrastructure can include a data collecting service agent that executes periodic collecting and transmission of serialized data into the cloud domain.
In addition, the collected data can be processed based on agent communication and service discovery capabilities for intelligently directing remote storage of the data into preconditions blobs. In one or more embodiments, agent reasoning and collective bargaining can be used to determine a data stage locale and subsequent retrieval. In such embodiments, the agents assume cloud web role and worker role responsibilities.
The agents can also discover fundamental associations between the collected data in the cloud infrastructure, and perform actions based in part on the discovered associations. This can include, for example, triggering intelligent alarms, generating recommended courses of action, or initiating a control output in response to a discovered condition based on the learned associations.
The cloud-based infrastructure can also include a set of web-based and/or browser-based tools for that allow an end user to retrieve, direct, and/or uncompress the data from the cloud.
To the accomplishment of the foregoing and related ends, certain illustrative aspects are described herein in connection with the following description and the annexed drawings. These aspects are indicative of various ways which can be practiced, all of which are intended to be covered herein. Other advantages and novel features may become apparent from the following detailed description when considered in conjunction with the drawings



BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a high-level overview of an industrial enterprise that leverages cloud-based services.
FIG. 2 is a general high-level overview of a cloud computing infrastructure that provides remote monitoring services.
FIG. 3 illustrates a system that leverages a cloud-based infrastructure to provide Software as a Service (SaaS) for remote monitoring services to customer manufacturing sites.
FIG. 4 illustrates an exemplary cloud agent that collects, packages, and sends industrial data to a cloud-based remote monitoring system using a generic, unified data packaging schema.
FIG. 5 illustrates an exemplary data packet generated by a cloud agent for moving industrial data to a cloud-based remote monitoring system.
FIG. 6A illustrates an exemplary interface display that can be provided by a cloud-based remote monitoring system for rendering an animated graphical representation of an industrial system.
FIG. 6B illustrates an exemplary interface display that can be provided by a cloud-based remote monitoring system for displaying tag names and associated values.
FIG. 7 illustrates an exemplary alarm display that can be provided by a cloud-based remote monitoring system.
FIG. 8 illustrates an exemplary live data display that can be provided by a cloud-based remote monitoring system.
FIG. 9 illustrates an exemplary interface display that can be provided a cloud-based remote monitoring system for displaying tag history by machine section.
FIG. 10 illustrates an exemplary alarm summary interface display that can be provided by a cloud-based remote monitoring system.
FIG. 11 illustrates an exemplary notification architecture that can be leveraged in connection with intelligent alarming.
FIG. 12 is a flowchart of an example methodology for moving industrial data from a plant floor to a cloud platform.
FIG. 13 is a flowchart of an example methodology for creating and using message queues on a cloud platform for storage and processing of industrial data.
FIG. 14 is an example computing environment.
FIG. 15 is an example networking environment.



DETAILED DESCRIPTION
The subject disclosure is now described with reference to the drawings, wherein like reference numerals are used to refer to like elements throughout. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding thereof. It may be evident, however, that the subject disclosure can be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to facilitate a description thereof.
As used in this application, the terms “component,” “system,” “platform,” “layer,” “controller,” “terminal,” “station,” “node,” “interface” are intended to refer to a computer-related entity or an entity related to, or that is part of, an operational apparatus with one or more specific functionalities, wherein such entities can be either hardware, a combination of hardware and software, software, or software in execution. For example, a component can be, but is not limited to being, a process running on a processor, a hard disk drive, multiple storage drives (of optical or magnetic storage medium) including affixed (e.g., screwed or bolted) or removably affixed solid-state storage drives; an object; an executable; a thread of execution; a computer-executable program, and/or a computer. By way of illustration, both an application running on a server and the server can be a component. One or more components can reside within a process and/or thread of execution, and a component can be localized on one computer and/or distributed between two or more computers. Also, components as described herein can execute from various computer readable storage media having various data structures stored thereon. The components may communicate via local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems via the signal). As another example, a component can be an apparatus with specific functionality provided by mechanical parts operated by electric or electronic circuitry which is operated by a software or a firmware application executed by a processor, wherein the processor can be internal or external to the apparatus and executes at least a part of the software or firmware application. As yet another example, a component can be an apparatus that provides specific functionality through electronic components without mechanical parts, the electronic components can include a processor therein to execute software or firmware that provides at least in part the functionality of the electronic components. As further yet another example, interface(s) can include input/output (I/O) components as well as associated processor, application, or Application Programming Interface (API) components. While the foregoing examples are directed to aspects of a component, the exemplified aspects or features also apply to a system, platform, interface, layer, controller, terminal, and the like.
As used herein, the terms “to infer” and “inference” refer generally to the process of reasoning about or inferring states of the system, environment, and/or user from a set of observations as captured via events and/or data. Inference can be employed to identify a specific context or action, or can generate a probability distribution over states, for example. The inference can be probabilistic—that is, the computation of a probability distribution over states of interest based on a consideration of data and events. Inference can also refer to techniques employed for composing higher-level events from a set of events and/or data. Such inference results in the construction of new events or actions from a set of observed events and/or stored event data, whether or not the events are correlated in close temporal proximity, and whether the events and data come from one or several event and data sources.
In addition, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or.” That is, unless specified otherwise, or clear from the context, the phrase “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, the phrase “X employs A or B” is satisfied by any of the following instances: X employs A; X employs B; or X employs both A and B. In addition, the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from the context to be directed to a singular form.
Furthermore, the term “set” as employed herein excludes the empty set; e.g., the set with no elements therein. Thus, a “set” in the subject disclosure includes one or more elements or entities. As an illustration, a set of controllers includes one or more controllers; a set of data resources includes one or more data resources; etc. Likewise, the term “group” as utilized herein refers to a collection of one or more entities; e.g., a group of nodes refers to one or more nodes.
Various aspects or features will be presented in terms of systems that may include a number of devices, components, modules, and the like. It is to be understood and appreciated that the various systems may include additional devices, components, modules, etc. and/or may not include all of the devices, components, modules etc. discussed in connection with the figures. A combination of these approaches also can be used.
FIG. 1 illustrates a high-level overview of an industrial enterprise that leverages cloud-based services. The enterprise comprises one or more industrial facilities 104, each having a number of industrial devices 108 and 110 in use. The industrial devices 108 and 110 can make up one or more automation systems operating within the respective facilities 104. Exemplary automation systems can include, but are not limited to, batch control systems (e.g., mixing systems), continuous control systems (e.g., PID control systems), or discrete control systems. Industrial devices 108 and 110 can include such devices as industrial controllers (e.g., programmable logic controllers or other types of programmable automation controllers); field devices such as sensors and meters; motor drives; operator interfaces (e.g., human-machine interfaces, industrial monitors, graphic terminals, message displays, etc.); industrial robots, barcode markers and readers; vision system devices (e.g., vision cameras); smart welders; or other such industrial devices.
Exemplary automation systems can include one or more industrial controllers that facilitate monitoring and control of their respective processes. The controllers exchange data with the field devices using native hardwired I/O or via a plant network such as Ethernet/IP, Data Highway Plus, ControlNet, Devicenet, or the like. A given controller typically receives any combination of digital or analog signals from the field devices indicating a current state of the devices and their associated processes (e.g., temperature, position, part presence or absence, fluid level, etc.), and executes a user-defined control program that performs automated decision-making for the controlled processes based on the received signals. The controller then outputs appropriate digital and/or analog control signaling to the field devices in accordance with the decisions made by the control program. These outputs can include device actuation signals, temperature or position control signals, operational commands to a machining or material handling robot, mixer control signals, motion control signals, and the like. The control program can comprise any suitable type of code used to process input signals read into the controller and to control output signals generated by the controller, including but not limited to ladder logic, sequential function charts, function block diagrams, structured text, or other such platforms.
Although the exemplary overview illustrated in FIG. 1 depicts the industrial devices 108 and 110 as residing in fixed-location industrial facilities 104, the industrial devices 108 and 110 may also be part of a mobile control application, such as a system contained in a truck or other service vehicle.
According to one or more embodiments of this disclosure, industrial devices 108 and 110 can be coupled to a cloud platform 102 in order to leverage cloud-based applications. That is, the industrial devices 108 and 110 can be configured to discover and interact with cloud-based computing services 112 hosted by cloud platform 102. Cloud platform 102 can be any infrastructure that allows computing services 112 to be accessed and utilized by cloud-capable devices. Cloud platform 102 can be a public cloud accessible via the Internet by devices having Internet connectivity and appropriate authorizations to utilize the services 112. In some scenarios, cloud platform 102 can be provided by a cloud provider as a platform-as-a-service (PaaS), and the services 112 (such as the operator interface system described herein) can reside and execute on the cloud platform 102 as a cloud-based service. In some such configurations, access to the cloud platform 102 and the services 112 can be provided to customers as a subscription service by an owner of the services 112. Alternatively, cloud platform 102 can be a private cloud operated internally by the enterprise. An exemplary private cloud can comprise a set of servers hosting the cloud services 112 and residing on a corporate network protected by a firewall.
Cloud services 112 can include, but are not limited to, data storage, data analysis, control applications (e.g., applications that can generate and deliver control instructions to industrial devices 108 and 110 based on analysis of real-time system data or other factors), visualization applications such as the cloud-based operator interface system described herein, reporting applications, Enterprise Resource Planning (ERP) applications, notification services, or other such applications. If cloud platform 102 is a web-based cloud, industrial devices 108 and 110 at the respective industrial facilities 104 may interact with cloud services 112 directly or via the Internet. In an exemplary configuration, industrial devices 108 and 110 may access the cloud services 112 through on-premise cloud agents 106 at the respective industrial facilities 104, where the industrial devices 108 and 110 connect to the on-premise cloud agents 106 through a physical or wireless local area network or radio link. In another exemplary configuration, the industrial devices may access the cloud platform directly using an integrated cloud interface.
Providing industrial devices with cloud capability can offer a number of advantages particular to industrial automation. For one, cloud-based storage offered by the cloud platform can be easily scaled to accommodate the large quantities of data generated daily by an industrial enterprise. Moreover, multiple industrial facilities at different geographical locations can migrate their respective automation data to the cloud for aggregation, collation, collective analysis, and enterprise-level reporting without the need to establish a private network between the facilities. Industrial devices 108 and 110 having smart configuration capability can be configured to automatically detect and communicate with the cloud platform 102 upon installation at any facility, simplifying integration with existing cloud-based data storage, analysis, or reporting applications used by the enterprise. In another exemplary application, cloud-based diagnostic applications can monitor the health of respective automation systems or their associated industrial devices across an entire plant, or across multiple industrial facilities that make up an enterprise. Cloud-based lot control applications can be used to track a unit of product through its stages of production and collect production data for each unit as it passes through each stage (e.g., barcode identifier, production statistics for each stage of production, quality test data, abnormal flags, etc.). These industrial cloud-computing applications are only intended to be exemplary, and the systems and methods described herein are not limited to these particular applications. The cloud platform 102 can allow software vendors to provide software as a service, removing the burden of software maintenance, upgrading, and backup from their customers.
Maintaining stability and integrity of the physical equipment comprising a manufacturing environment is a high priority for most industrial enterprises. To this end, it would be beneficial to monitor and forecast conditions of the various industrial systems and the devices that make up those systems to prevent harmful or catastrophic events from occurring (e.g., events that may result in machine downtime, sub-standard product quality, etc.). Remote monitoring of these industrial assets would allow plant personnel to view plant data generated by their systems from a remote location, and could facilitate remote notification in response to a detected system event requiring attention. However, on-premise data collection required by such remote monitoring systems consumes large amounts of data storage. Moreover, since such a remote monitoring system could involve transmission of potentially sensitive plant data to a remote viewer, secure data transmission channels would be required.
Also, some remote monitoring services depend on heavily customized systems and interfaces, which can be monolithic and expensive. Such remote monitoring services using custom-based technology can be expensive and difficult to expand without forcing a full re-programming of the application and its interfaces. For example, if a plant enterprise expanded their automation systems (e.g., by adding a new production line, adding new data points to an existing production line, etc.), it would be necessary to redevelop any customized remote monitoring systems in place to include the new systems or data points. The redeveloped monitoring system would then have to be retested and re-deployed to facilitate monitoring of the newly expanded automation system. Conventionally, these modifications often must be implemented by a hired software developer, and thus would incur additional costs.
To address these and other issues, one or more embodiments of the present application provide a cloud computing infrastructure for remote monitoring services using infrastructure constructs. FIG. 2 illustrates a general high-level overview of such a cloud computing infrastructure. In this exemplary architecture, a number of industrial assets reside on a plant network 224 in a manufacturing environment. These assets can include industrial controllers 210 and 220 that monitor and control I/O device 212 and 222, a data server 214, a motor drive 216, and a remote I/O interface 218 that remotely interfaces a group of I/O devices 226 to one or more of the industrial controllers 210 or 220. Although the illustrated example depicts a set of specific industrial devices residing on plant network 224, it is to be appreciated that embodiments of the present application are not limited to interaction with this particular set of industrial equipment, and that the systems and methods described herein are suitable for industrial environments comprising any combination of industrial assets.
Also located on the plant facility is a cloud agent 208 that provides on-premise data collection, packaging, and transmission of industrial data generated by the industrial assets. Cloud agent 208 acts as a generic gateway to collect data items from the various industrial assets on plant network 224 and packages the collected data according to a generic, uniform data packaging schema used to move the on-premise data to a cloud platform 204 via the Internet 206. Once the packaged data has been provided to cloud platform 204, the data can be retrieved or viewed from a remote monitoring center 202. Cloud agent 208 provides a software mechanism to dynamically link on-premise-to-cloud gateways. As will be described in more detail below, cloud agent 208 provides an expandable data type schema that allows new data types to be added without the need to redeploy the monitoring system to the cloud.
FIG. 3 illustrates a system that leverages a cloud-based infrastructure to provide Software as a Service (SaaS) for remote monitoring services to customer manufacturing sites. This system can provide remote monitoring services in connection with alarm and event notification for critical industrial assets, historical data collection, remote system access, and other such applications.
In the example illustrated in FIG. 3, a data historian 304 collects site data from one or more assets (e.g., data generated by one or more industrial controllers, such as industrial controllers 210 and 220) at a plant facility. For example, data historian 304 can monitor one or more controller tags defined in a tags archive and store data in local storage associated with data historian 304. This can include both historical data (e.g., alarm history, status history, trend data, etc.) as well as live data values read from the controller(s).
An on-premise cloud agent 306 is configured to collect the live or historical data from the controllers, either directly or by accessing data historian 304. The process of collecting the data involves intelligent sorting and organizing based on defined criteria, including but not limited to time of occurrence and/or user-defined priorities. Cloud agent 306 can be, for example, a service (e.g., a Windows service) that periodically collects and transmits serialized and compressed data into the cloud domain using standard web services over HTTPS/SSL. FIG. 3 depicts data historian 304 as the data source for cloud agent 306. This configuration can be useful if there are a large number of data points to monitor. However, some embodiments of cloud agent 306 can collect data directly from the manufacturing assets themselves (e.g., through a Common Industrial Protocol link), or through middleware applications such as OPC clients.
Cloud agent 306 is illustrated in more detail with reference to FIG. 4. As noted above, site data 410 is collected by a data historian 304 at the plant facility 302. Cloud agent 306 comprises collection services 414 that collect device data, either from data historian 304 or directly from the devices themselves (e.g., variable frequency drives 412 in the illustrated example) via a common industrial protocol (CIP) link or other suitable communication protocol. Collection services 414 can then compress the data and store the data in a compressed data file 422. Queue processing services 416 can read the compressed data file 422 and reference a message queuing database 420, which manages customer site configuration and subscription to the remote monitoring system. Based on configuration information in the message queuing database 420, queue processing services 416 package the compressed data file 422 into a data packet and push the data packet 320 to the cloud platform. An exemplary data packet 502 is illustrated in FIG. 5. In addition to compressed data file 506, data packet 502 can include a header 504 that includes customer-specific data read from message queuing database 420. For example, header 504 can include a unique customer ID, a site ID representing a particular plant facility, a virtual support engineer ID, a data priority for the data in the compressed data file, a message type, and a process ID. Packaging the data in this way can allow data from diverse data sources to be packaged together using a uniform, generic data packaging schema so that the data can be moved to the cloud infrastructure.
Message queuing database 420 can include site-specific information regarding what tag data are to be collected (e.g., data tag identifiers, etc.), user-defined priorities or data types for the data tags, firewall settings that allow cloud agent 306 to communicate with the cloud platform, and other such configuration information. Configuration information in message queuing database 420 instructs cloud agent 306 how to talk to the data tags and to the remote monitoring service on the cloud platform.
In one or more embodiments, in addition to collection and migration of data, cloud agent 306 can also perform local analytics on the data prior to moving the data to the cloud platform. This can comprise substantially any type of pre-processing or data refinement that may facilitate more efficient transfer of the data to the cloud, prepare the data for enhanced analysis in the cloud, reduce the amount of cloud storage required to store the data, or other such benefits. For example, cloud agent 306 may be configured to compress the collected data using any suitable data compression algorithm prior to migrating the data to the cloud platform. This can include detection and deletion of redundant data bits, truncation of precision bits, or other suitable compression operations. In another example, cloud agent 306 may be configured to aggregate data by combining related data from multiple sources. For example, data from multiple sensors measuring related aspects of an automation system can be identified and aggregated into a single cloud upload packet by cloud agent 306. Cloud agent 306 may also encrypt sensitive data prior to upload to the cloud. In yet another example, cloud agent 306 may filter the data according to any specified filtering criterion (e.g., filtering criteria defined in a filtering profile). For example, defined filtering criteria may specify that pressure values exceeding a defined setpoint are to be filtered out prior to uploading the pressure values to the cloud.
In some embodiments, cloud agent 306 may also transform a specified subset of the industrial data from a first format to a second format in accordance with a requirement of a cloud-based analysis application. For example, a cloud-based reporting application may require measured values in ASCII format. Accordingly, cloud agent 306 can convert a selected subset of the gathered data from floating point format to ASCII prior to pushing the data to the cloud platform for storage and processing. Converting the raw data at the industrial device before uploading to the cloud, rather than requiring this transformation to be performed on the cloud, can reduce the amount of processing load on the cloud side.
Cloud agent 306 may also associate metadata with selected subsets of the data prior to migration to the cloud, thereby contextualizing the data within the industrial environment. For example, cloud agent 306 can tag selected subsets of the data with a time indicator specifying a time at which the data was generated, a quality indicator, a production area indicator specifying a production area within the industrial enterprise from which the data was collected, a machine or process state indicator specifying a state of a machine or process at the time the data was generated, a personnel identifier specifying an employee on duty at the time the data was generated, or other such contextual metadata. In this way, cloud agent 306 can perform layered processing of the collected data to generate meta-level knowledge that can subsequently be leveraged by cloud-based analysis tools to facilitate enhanced analysis of the data in view of a larger plant context.
Returning now to FIG. 3, cloud agent 306 sends data packet 320 to the cloud-based remote-monitoring system on cloud platform 308. Processing of the data is based on agent communication and service discovery capabilities for intelligently directing remote storage of the data into preconditioned cloud blobs 316. The infrastructure can use agent reasoning and collective bargain features to determine a data storage locale and subsequent retrieval.
Through the configuration interface provided by cloud agent 306, users at the plant facility 302 can dynamically configure one or more message queues 314 that respectively define how the data is processed in the cloud platform 308. In the present example, separate queues have been defined for alarms, live data, historical data, and motor drive data. The historical data queue relates to time-series records, which can be accessed through an application programming interface (API) (e.g., a structured query language (SQL) API or other suitable API). The alarms queue relates to abnormal situations, where the alarm data can also be accessed through the API. This alarms queue can comprise multiple queues associated with different alarm priorities, to allow for individual processing for different alarms having different levels of criticality. In some embodiments, servers, controllers, switches, etc., can be monitored using a number of protocols, and at a certain point (e.g., at the end of a monitoring cycle) alarms can be queued up and cloud agent 306 can send the alarms to the cloud. Alarms can be reactive (e.g., alarms that trigger when a motor fails, when a CPU crashes, when an interlock is tripped, etc.) or proactive (e.g., track consumables on a machine and generate an alarm when time to reorder, monitor cycle counts on a machine and generate an alarm when to schedule preventative maintenance, generate an alarm when temperatures go out of defined bandwidths, send a notification when a computer's memory is 80% full, etc.).
The live data queue relates to substantially real-time monitored data, such as current temperatures, current pressures, etc. The live data values can also be accessed through the API (e.g., a SQL API). The motor drives queue is specific to motor drive data, and can be accessed, for example, through a deep packet inspection (DPI) protocol to the respective drives in the illustrated example. In some example systems, the motor drive data can relate to alarming and uploading of drive parameter data via a connector that uses the DPI protocol via a .Net class provided by the drives group.
Cloud agent 306 can allow the user to define these queues from the on-site location and to define how data in each queue is handled. For example, the user can define, for each queue, an upload frequency, a priority level (e.g., which data queues should take processing priority over other data queues), which cloud partitions or databases data from the respective queues should be placed in, and other such information. In an exemplary scenario, the live data queue may be defined to process live data values that are to be used by a remote operator interface application to view substantially real-time data from the plant facility 302, while historical data queue may be used to process historian data for archival storage in a historical database 328 on cloud storage. Accordingly, the live data queue may be assigned a higher priority relative to the historical data queue, since data in the live data queue is more time-critical than data in the historical queue.
Through cloud agent 306, users can assign priorities to respective data tags or tag groups at the customer site. These priority assignments can be stored in the message queuing database 420 of the cloud agent 306. Accordingly, when queue processing services 416 package the collected data to be moved to the cloud platform, the collected data items can be packaged into data packets according to priority (as defined in message queuing database 420), and the respective data packet headers populated with the appropriate priority level. If access to the cloud is disconnected, data will continue to be collected by collection services 414 and stored locally at local storage associated with collections services. When communication to the cloud is restored, the stored data will be forwarded to cloud storage. Queue processing services can also encrypt and send storage account keys to the cloud platform for user verification.
When cloud agent 306 sends a data packet to the cloud-based remote monitoring service, the service reads the data header information to determine a priority assigned to the data (e.g., as defined in the data priority field of the data packet) and sends the data packet (or the compressed data therein) to a selected one of the user defined message queues 314 based on the priority. On the other side of the message queues 314, a worker role 322 processes data in the respective queues according to the predefined processing definitions. Worker role 322 determines how the queued data is to be processed based on behavior assemblies 324 stored in a customer-specific manifest. Behavior assemblies 324 define and implement customer-specific capabilities and preferences for processing monitored data. Behavior assemblies 324 can be dynamically uploaded by a user at the plant facility 302 through cloud agent 306, which facilitates dynamic extension of SaaS cloud computing capability.
For example, if new data points are to be added to the remote monitoring system that require creation of a new data queue, the user can interact with cloud agent 306 to configure a new behavior assembly for the new queue that defines such aspects as processing priority for the data, upload frequency for the data, where the data is to be stored within cloud storage 326, and other such information. Cloud agent 306 can then upload the new behavior assembly together with the data (or independently of the data). The new behavior assembly is then added to the customer's manifest with the other behavior assemblies 324 defined for the customer, so that worker role 322 can leverage the new behavior assembly to determine how data in the new queue is to be processed. This new behavior assembly need only be uploaded to the cloud-based remote monitoring service once. Thereafter, data placed in the new message queue (of message queues 314) will be processed by worker role 322 according to the new behavior assembly stored in the customer's manifest. For example, the behavior assembly may define where the data is to be stored within cloud storage 326 (e.g., in historical database 328 or in Alarms and Live Data database 334), and whether processing of the new data queue is to take priority over other data queues. In some embodiments, the manifest may only accept a new behavior assembly if the behavior assembly is accompanied by a unique key associated with the client.
Partitioning of cloud storage 326 can be configured by a management console 332, which can write partitioning definitions to a system database associated with the cloud storage 326.
Once the cloud-based remote monitoring infrastructure has processed and stored the data provided by cloud agent 306 according to the techniques described above, the data can be made accessible to client devices 330 for viewing. Data analysis on the cloud platform 308 can provide a set of web-based and browser enabled technologies for retrieving, directing, and uncompressing the data from the cloud platform 308 to the client devices 330. To this end, reporting services 318 can deliver data in cloud storage 326 (e.g., from the Alarm and Live Data database 334 or historical database 328) to the client devices 330 in a defined format. For example, reporting services 318 can leverage monitored data stored in cloud storage 326 to provide remote operator interfaces to client devices 330 over the Internet.
FIGS. 6A and 6B illustrate an exemplary interface displays that can be provided by reporting services 318. The interface display 602 of FIG. 6A displays an animated graphical representation of a section of an industrial system, and interface display 604 lists a set of relevant data tags and their respective values for data points rendered on display interface 602. Reporting services 318 can populate display interfaces 602 and 604 with appropriate data from cloud storage 326 and deliver the display interfaces to client devices 330 having suitable access permissives to access the data.
FIG. 7 illustrates an exemplary alarm display 700 that can be provided by reporting services 318 based on data in cloud storage 326. As with displays 604 and 602, reporting services 318 can deliver alarm display 700 to suitable client devices 330 having suitable authorization to view the alarm data. FIG. 8 illustrates an exemplary live data display 800 that can be provided by reporting services 318. The alarm data rendered on alarm display 700 and live data rendered on live data display 800 can be drawn from the Alarms and Live Data database 334 on cloud storage 326.
FIG. 9 illustrates an exemplary interface display 900 that can be provided by reporting services 318 and that lists tag history by machine section. Tag data in the respective columns of interface display 900 can be drawn from historical database 328 on cloud storage 326.
FIG. 10 illustrates an exemplary alarm summary interface display 1000 that can be provided by reporting services 318. Alarm summary interface display 1000 can render graphical representations of alarm summaries based on data in historical database 328.
It is to be appreciated that the interfaces illustrated in FIGS. 6-10 are only intended to be exemplary, and that any suitable display format for plant data collected and stored in the cloud infrastructure are within the scope of one or more embodiments of this disclosure.
Using the cloud agent framework described above, users can organize the cloud computing infrastructure at the plant facility through cloud agent 306 without the need to redevelop, recompile, test, and re-upload the remote monitoring applications. Cloud agent 306 provides a mechanism to integrate industrial devices or historians (such as historian 304) with the remote monitoring cloud infrastructure, where data from plant-side devices and historians can be leveraged by cloud-based applications and services. By offering users the ability to create and upload behavior assemblies for respective data types, cloud agent 306 can facilitate dynamic allocation of cloud computing data storage and computing resources for plant data without the need to redeploy the remote monitoring application whenever functional changes are implemented. This can remove several engineering and architectural costs associated with implementation or re-scaling of a remote monitoring service.
Some embodiments of cloud agent 306 and the associated remote monitoring infrastructure can also facilitate intelligent alarming. For example, cloud agent 306 can analyze the collected data, discover fundamental associations between data items, and determine a next step of action so that alarms can be processed, notifications can be sent from the cloud platform 308 to the client devices 330, or other such responses. For example, in some embodiments, the cloud-based remote monitoring infrastructure can generate e-mail notifications sent using a SendGrid service or other such service.
FIG. 11 illustrates an exemplary notification architecture that can be leveraged in connection with intelligent alarming according to one or more embodiments of this disclosure. In this example system, reporting services 1102 (similar to reporting services 318 of FIG. 3) residing on the cloud platform can include a notification component 1104 and an analytics component 1106. Analytics component 1106 can determine whether selected subsets of industrial data 1110 stored on cloud storage 1112 (similar to cloud storage 326 of FIG. 3) meet one or more predefined notification conditions. These can include such conditions as detecting that a particular process value has exceeded a defined setpoint, detecting a transition to a particular machine state, detecting an alarm condition, determining that a specified production goal has been achieved, or other such conditions that can be detected through analysis of the industrial data 1110. When an actionable condition is detected within the industrial data 1110, analytics component 1106 can inform notification component 1104 that personnel are to be notified. In response, notification component 1104 can identify one or more specific plant employees who are to receive the notification, as well as information identifying a user notification device, phone number, or email address for each person to be notified.
In one or more embodiments, notification component 1104 can determine this notification information by cross-referencing configuration data 1108 that identifies which personnel are to be notified for a given type of condition, one or more notification methods for each identified person, and/or other relevant information. When analytics component 1106 determines that a subset of the industrial data 1110 requires action to be taken by plant personnel, notification component 1104 can reference configuration data 1108 to determine, for example, which personnel should be notified, which user devices should receive the notification, a required action to be taken by the recipient, a due date for the action, a format for the notification, and/or other relevant information. Configuration data 1108 can maintain multiple separate personnel lists respectively associated with different types of actionable situations. In some embodiments, the personnel list selected for a given notification can be at least partly a function of context data associated with the relevant subset of industrial data 1110. For example, if industrial data 1110 indicates that a process parameter has exceeded a setpoint value, notification component 1104 can identify the list of personnel to receive the notification based on the area or workcell to which the process parameter relates.
Once the appropriate personnel and devices to be notified have been determined, notification component 1104 can deliver notifications 1114 to one or more notification destinations. The notification can be sent to an Internet-capable client device 1118, such as a phone, a tablet computer, a desktop computer, or other suitable devices. In some embodiments, a cloud application running on the cloud platform can provide a mechanism for notified personnel to communicate with one another via the cloud (e.g., establish a conference call using Voice-over-IP). Notification component 1104 can also be configured to send the notification 1114 periodically at a defined frequency until the recipient positively responds to the notification (e.g., by sending a manual acknowledgement via the client device 1118). The notification component 1104 can also be configured to escalate an urgency of high-priority notifications if an acknowledgment is not received within a predetermined amount of time. This urgency escalation can entail sending the notification 1114 at a gradually increasing frequency, sending the notification to devices associated with secondary personnel if the primary personnel do not respond within a defined time period, or other such escalation measures.
FIGS. 12-13 illustrate various methodologies in accordance with one or more embodiments of the subject application. While, for purposes of simplicity of explanation, the one or more methodologies shown herein are shown and described as a series of acts, it is to be understood and appreciated that the subject innovation is not limited by the order of acts, as some acts may, in accordance therewith, occur in a different order and/or concurrently with other acts from that shown and described herein. For example, those skilled in the art will understand and appreciate that a methodology could alternatively be represented as a series of interrelated states or events, such as in a state diagram. Moreover, not all illustrated acts may be required to implement a methodology in accordance with the innovation. Furthermore, interaction diagram(s) may represent methodologies, or methods, in accordance with the subject disclosure when disparate entities enact disparate portions of the methodologies. Further yet, two or more of the disclosed example methods can be implemented in combination with each other, to accomplish one or more features or advantages described herein.
FIG. 12 illustrates an example methodology 1200 for moving industrial data from a plant floor to a cloud platform. Initially, at 1202, industrial data is collected from one or more industrial devices on a plant floor. At 1204, the industrial data is stored in a compressed file. The industrial data can be compressed, for example by collection services of a cloud agent that provides on-premise data collection, packaging, and transmission of industrial data generated by industrial assets on the plant floor.
At 1206, the compressed data file is packaged (e.g., by the cloud agent) into a data packet. At 1208, the compressed file is assigned to a message queue based on at least one of a data type or a priority associated with the collected industrial data. The message queue comprises a queue defined on a cloud platform for storage and processing of data in accordance with an associated behavior assembly.
At 1210, a header is appended to the data packet indicating the message queue assigned at step 1208. At 1212, the data packet including the header appended at step 1210 is sent to a cloud platform that maintains the assigned message queue. At 1214, the industrial data contained in the data packet is stored in the message queue on the cloud platform in accordance with the header. Once stored in the message queue, the data can be processed on the cloud platform according to predefined processing definitions associated with the assigned message queue.
FIG. 13 illustrates an example methodology 1300 for creating and using message queues on a cloud platform for storage and processing of industrial data. Initially, at 1302, an instruction to create a message queue is received at a cloud platform. The instruction can be received, for example, by a cloud agent executing on at an industrial enterprise. At 1304, the message queue is created on the cloud platform in accordance with the instruction received at step 1302. At 1306, a behavior assembly defining a processing to be associated with the message queue is received at the cloud platform. At 1308, the behavior assembly is maintained in a customer-specific manifest on the cloud platform.
At 1310, a data packet containing industrial data and a header specifying the message queue is received at the cloud platform. At 1312, the industrial data contained in the data packet received at step 1310 is assigned to the message queue in accordance with the header. At 1314, the industrial data maintained in the message queue is processed on the cloud platform in accordance with the behavior assembly maintained in the customer-specific manifest.
Embodiments, systems, and components described herein, as well as industrial control systems and industrial automation environments in which various aspects set forth in the subject specification can be carried out, can include computer or network components such as servers, clients, programmable logic controllers (PLCs), communications modules, mobile computers, wireless components, control components and so forth which are capable of interacting across a network. Computers and servers include one or more processors—electronic integrated circuits that perform logic operations employing electric signals—configured to execute instructions stored in media such as random access memory (RAM), read only memory (ROM), a hard drives, as well as removable memory devices, which can include memory sticks, memory cards, flash drives, external hard drives, and so on.
Similarly, the term PLC as used herein can include functionality that can be shared across multiple components, systems, and/or networks. As an example, one or more PLCs can communicate and cooperate with various network devices across the network. This can include substantially any type of control, communications module, computer, Input/Output (I/O) device, sensor, actuator, and human machine interface (HMI) that communicate via the network, which includes control, automation, and/or public networks. The PLC can also communicate to and control various other devices such as I/O modules including analog, digital, programmed/intelligent I/O modules, other programmable controllers, communications modules, sensors, actuators, output devices, and the like.
The network can include public networks such as the internet, intranets, and automation networks such as control and information protocol (CIP) networks including DeviceNet, ControlNet, and Ethernet/IP. Other networks include Ethernet, DH/DH+, Remote I/O, Fieldbus, Modbus, Profibus, CAN, wireless networks, serial protocols, and so forth. In addition, the network devices can include various possibilities (hardware and/or software components). These include components such as switches with virtual local area network (VLAN) capability, LANs, WANs, proxies, gateways, routers, firewalls, virtual private network (VPN) devices, servers, clients, computers, configuration tools, monitoring tools, and/or other devices.
In order to provide a context for the various aspects of the disclosed subject matter, FIGS. 14 and 15 as well as the following discussion are intended to provide a brief, general description of a suitable environment in which the various aspects of the disclosed subject matter may be implemented.
With reference to FIG. 14, an example environment 1410 for implementing various aspects of the aforementioned subject matter includes a computer 1412. The computer 1412 includes a processing unit 1414, a system memory 1416, and a system bus 1418. The system bus 1418 couples system components including, but not limited to, the system memory 1416 to the processing unit 1414. The processing unit 1414 can be any of various available processors. Dual microprocessors and other multiprocessor architectures also can be employed as the processing unit 1414.
The system bus 1418 can be any of several types of bus structure(s) including the memory bus or memory controller, a peripheral bus or external bus, and/or a local bus using any variety of available bus architectures including, but not limited to, 8-bit bus, Industrial Standard Architecture (ISA), Micro-Channel Architecture (MSA), Extended ISA (EISA), Intelligent Drive Electronics (IDE), VESA Local Bus (VLB), Peripheral Component Interconnect (PCI), Universal Serial Bus (USB), Advanced Graphics Port (AGP), Personal Computer Memory Card International Association bus (PCMCIA), and Small Computer Systems Interface (SCSI).
The system memory 1416 includes volatile memory 1420 and nonvolatile memory 1422. The basic input/output system (BIOS), containing the basic routines to transfer information between elements within the computer 1412, such as during start-up, is stored in nonvolatile memory 1422. By way of illustration, and not limitation, nonvolatile memory 1422 can include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable PROM (EEPROM), or flash memory. Volatile memory 1420 includes random access memory (RAM), which acts as external cache memory. By way of illustration and not limitation, RAM is available in many forms such as synchronous RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM (DRRAM).
Computer 1412 also includes removable/non-removable, volatile/non-volatile computer storage media. FIG. 14 illustrates, for example a disk storage 1424. Disk storage 1424 includes, but is not limited to, devices like a magnetic disk drive, floppy disk drive, tape drive, Jaz drive, Zip drive, LS-100 drive, flash memory card, or memory stick. In addition, disk storage 1424 can include storage media separately or in combination with other storage media including, but not limited to, an optical disk drive such as a compact disk ROM device (CD-ROM), CD recordable drive (CD-R Drive), CD rewritable drive (CD-RW Drive) or a digital versatile disk ROM drive (DVD-ROM). To facilitate connection of the disk storage 1424 to the system bus 1418, a removable or non-removable interface is typically used such as interface 1426.
It is to be appreciated that FIG. 14 describes software that acts as an intermediary between users and the basic computer resources described in suitable operating environment 1410. Such software includes an operating system 1428. Operating system 1428, which can be stored on disk storage 1424, acts to control and allocate resources of the computer 1412. System applications 1430 take advantage of the management of resources by operating system 1428 through program modules 1432 and program data 1434 stored either in system memory 1416 or on disk storage 1424. It is to be appreciated that one or more embodiments of the subject disclosure can be implemented with various operating systems or combinations of operating systems.
A user enters commands or information into the computer 1412 through input device(s) 1436. Input devices 1436 include, but are not limited to, a pointing device such as a mouse, trackball, stylus, touch pad, keyboard, microphone, joystick, game pad, satellite dish, scanner, TV tuner card, digital camera, digital video camera, web camera, and the like. These and other input devices connect to the processing unit 1414 through the system bus 1418 via interface port(s) 1438. Interface port(s) 1438 include, for example, a serial port, a parallel port, a game port, and a universal serial bus (USB). Output device(s) 1440 use some of the same type of ports as input device(s) 1436. Thus, for example, a USB port may be used to provide input to computer 1412, and to output information from computer 1412 to an output device 1440. Output adapters 1442 are provided to illustrate that there are some output devices 1440 like monitors, speakers, and printers, among other output devices 1440, which require special adapters. The output adapters 1442 include, by way of illustration and not limitation, video and sound cards that provide a means of connection between the output device 1440 and the system bus 1418. It should be noted that other devices and/or systems of devices provide both input and output capabilities such as remote computer(s) 1444.
Computer 1412 can operate in a networked environment using logical connections to one or more remote computers, such as remote computer(s) 1444. The remote computer(s) 1444 can be a personal computer, a server, a router, a network PC, a workstation, a microprocessor based appliance, a peer device or other common network node and the like, and typically includes many or all of the elements described relative to computer 1412. For purposes of brevity, only a memory storage device 1446 is illustrated with remote computer(s) 1444. Remote computer(s) 1444 is logically connected to computer 1412 through a network interface 1448 and then physically connected via communication connection 1450. Network interface 1448 encompasses communication networks such as local-area networks (LAN) and wide-area networks (WAN). LAN technologies include Fiber Distributed Data Interface (FDDI), Copper Distributed Data Interface (CDDI), Ethernet/IEEE 802.3, Token Ring/IEEE 802.5 and the like. WAN technologies include, but are not limited to, point-to-point links, circuit switching networks like Integrated Services Digital Networks (ISDN) and variations thereon, packet switching networks, and Digital Subscriber Lines (DSL).
Communication connection(s) 1450 refers to the hardware/software employed to connect the network interface 1448 to the system bus 1418. While communication connection 1450 is shown for illustrative clarity inside computer 1412, it can also be external to computer 1412. The hardware/software necessary for connection to the network interface 1448 includes, for exemplary purposes only, internal and external technologies such as, modems including regular telephone grade modems, cable modems and DSL modems, ISDN adapters, and Ethernet cards.
FIG. 15 is a schematic block diagram of a sample-computing environment 1500 with which the disclosed subject matter can interact. The sample-computing environment 1500 includes one or more client(s) 1510. The client(s) 1510 can be hardware and/or software (e.g., threads, processes, computing devices). The sample-computing environment 1500 also includes one or more server(s) 1530. The server(s) 1530 can also be hardware and/or software (e.g., threads, processes, computing devices). The servers 1530 can house threads to perform transformations by employing one or more embodiments as described herein, for example. One possible communication between a client 1510 and servers 1530 can be in the form of a data packet adapted to be transmitted between two or more computer processes. The sample-computing environment 1500 includes a communication framework 1550 that can be employed to facilitate communications between the client(s) 1510 and the server(s) 1530. The client(s) 1510 are operably connected to one or more client data store(s) 1560 that can be employed to store information local to the client(s) 1510. Similarly, the server(s) 1530 are operably connected to one or more server data store(s) 1540 that can be employed to store information local to the servers 1530.
What has been described above includes examples of the subject innovation. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing the disclosed subject matter, but one of ordinary skill in the art may recognize that many further combinations and permutations of the subject innovation are possible. Accordingly, the disclosed subject matter is intended to embrace all such alterations, modifications, and variations that fall within the spirit and scope of the appended claims.
In particular and in regard to the various functions performed by the above described components, devices, circuits, systems and the like, the terms (including a reference to a “means”) used to describe such components are intended to correspond, unless otherwise indicated, to any component which performs the specified function of the described component (e.g., a functional equivalent), even though not structurally equivalent to the disclosed structure, which performs the function in the herein illustrated exemplary aspects of the disclosed subject matter. In this regard, it will also be recognized that the disclosed subject matter includes a system as well as a computer-readable medium having computer-executable instructions for performing the acts and/or events of the various methods of the disclosed subject matter.
In addition, while a particular feature of the disclosed subject matter may have been disclosed with respect to only one of several implementations, such feature may be combined with one or more other features of the other implementations as may be desired and advantageous for any given or particular application. Furthermore, to the extent that the terms “includes,” and “including” and variants thereof are used in either the detailed description or the claims, these terms are intended to be inclusive in a manner similar to the term “comprising.”
In this application, the word “exemplary” is used to mean serving as an example, instance, or illustration. Any aspect or design described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects or designs. Rather, use of the word exemplary is intended to present concepts in a concrete fashion.
Various aspects or features described herein may be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques. The term “article of manufacture” as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier, or media. For example, computer readable media can include but are not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips . . . ), optical disks [e.g., compact disk (CD), digital versatile disk (DVD) . . . ], smart cards, and flash memory devices (e.g., card, stick, key drive . . . ).
As used in this application, the terms “component,” “system,” “platform,” “layer,” “controller,” “terminal,” “station,” “node,” “interface” are intended to refer to a computer-related entity or an entity related to, or that is part of, an operational apparatus with one or more specific functionalities, wherein such entities can be either hardware, a combination of hardware and software, software, or software in execution. For example, a component can be, but is not limited to being, a process running on a processor, a processor, a hard disk drive, multiple storage drives (of optical or magnetic storage medium) including affixed (e.g., screwed or bolted) or removable affixed solid-state storage drives; an object; an executable; a thread of execution; a computer-executable program, and/or a computer. By way of illustration, both an application running on a server and the server can be a component. One or more components can reside within a process and/or thread of execution, and a component can be localized on one computer and/or distributed between two or more computers. Also, components as described herein can execute from various computer readable storage media having various data structures stored thereon. The components may communicate via local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems via the signal). As another example, a component can be an apparatus with specific functionality provided by mechanical parts operated by electric or electronic circuitry which is operated by a software or a firmware application executed by a processor, wherein the processor can be internal or external to the apparatus and executes at least a part of the software or firmware application. As yet another example, a component can be an apparatus that provides specific functionality through electronic components without mechanical parts, the electronic components can include a processor therein to execute software or firmware that provides at least in part the functionality of the electronic components. As further yet another example, interface(s) can include input/output (I/O) components as well as associated processor, application, or Application Programming Interface (API) components. While the foregoing examples are directed to aspects of a component, the exemplified aspects or features also apply to a system, platform, interface, layer, controller, terminal, and the like.
As used herein, the terms “to infer” and “inference” refer generally to the process of reasoning about or inferring states of the system, environment, and/or user from a set of observations as captured via events and/or data. Inference can be employed to identify a specific context or action, or can generate a probability distribution over states, for example. The inference can be probabilistic—that is, the computation of a probability distribution over states of interest based on a consideration of data and events. Inference can also refer to techniques employed for composing higher-level events from a set of events and/or data. Such inference results in the construction of new events or actions from a set of observed events and/or stored event data, whether or not the events are correlated in close temporal proximity, and whether the events and data come from one or several event and data sources.
In addition, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or.” That is, unless specified otherwise, or clear from the context, the phrase “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, the phrase “X employs A or B” is satisfied by any of the following instances: X employs A; X employs B; or X employs both A and B. In addition, the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from the context to be directed to a singular form.
Furthermore, the term “set” as employed herein excludes the empty set; e.g., the set with no elements therein. Thus, a “set” in the subject disclosure includes one or more elements or entities. As an illustration, a set of controllers includes one or more controllers; a set of data resources includes one or more data resources; etc. Likewise, the term “group” as utilized herein refers to a collection of one or more entities; e.g., a group of nodes refers to one or more nodes.
Various aspects or features will be presented in terms of systems that may include a number of devices, components, modules, and the like. It is to be understood and appreciated that the various systems may include additional devices, components, modules, etc. and/or may not include all of the devices, components, modules etc. discussed in connection with the figures. A combination of these approaches also can be used.

## Claims

1. A system for providing industrial data to a cloud-based remote monitoring application, comprising:
a memory that stores executable components; and
a processor, operatively coupled to the memory, that executes the executable components, the executable components comprising:
a collection component configured to collect industrial data from one or more industrial devices and store the industrial data in compressed files;
a queue processing component configured to package the compressed files into respective data packets and assign the compressed files to selected message queues, of a set of message queues defined on a cloud platform, based on classifications of the respective data packets as one of time-series record data, real-time monitored data, or alarm data, wherein the data packets comprise headers that indicate the selected message queues, and wherein the set of message queues comprise at least a historical data queue for processing of the time-series record data, a live data queue for processing of the real-time monitored data, and an alarms queue for processing of the alarm data, the alarms queue having a highest processing priority of the set of message queues; and

a communication component configured to send the data packets to the cloud platform.

2. The system of claim 1, wherein the queue processing component is further configured to determine the selected message queues based on a configuration file that defines associations between the message queues and at least one of a data type of the industrial data or a priority associated with the industrial data.

3. The system of claim 2, wherein the executable components further comprise an interface component configured to receive input that assigns the priority to respective data tags that contain the industrial data.

4. The system of claim 1, wherein the queue processing service is further configured to upload behavior assembly data to the cloud platform, wherein the behavior assembly data defines at least one of processing preferences or storage preferences associated with the set of message queues.

5. The system of claim 1, wherein the headers of the data packets respectively comprise fields for identifying one of the set of message queues and at least one of a customer identifier, a site identifier a virtual support engineer identifier, a data priority, a message type, or a process identifier.

6. The system of claim 1, wherein the executable components further comprise a local analytics component configured to at least one of append contextual metadata to the industrial data, filter the industrial data, re-format the industrial data, combine subsets of the industrial data, summarize the industrial data, or compress the industrial data prior to sending the industrial data to the cloud platform.

7. A system for remotely monitoring industrial data using a cloud platform, comprising:
a memory that stores executable components; and
a processor, operatively coupled to the memory, that executes the executable components, the executable components comprising:
a queue management component configured to maintain data queues on a cloud platform, the data queues comprising at least a historical data queue for processing of time-series record data, a live data queue for processing of real-time monitored data, and an alarms queue for processing of alarm data, wherein the data queues are associated with respective processing priorities, and wherein the alarm queue is assigned a highest processing priority of the data queues; and
a receiving component configured to receive, at the cloud platform, data packets from a cloud agent device, wherein the data packets respectively comprise industrial data and a header for the industrial data, and the receiving component is further configured to classify the data packets, based on the header, according to time-series record data, real-time monitored data, and alarm data, and to assign the industrial data associated with the respective data packets to selected queues of the data queues based on classifications of the data packets.

8. The system of claim 7, wherein the executable components further comprise a worker role component configured to process the data packets according to behavior assembly data associated with respective data queues of the data queues.

9. The system of claim 8, wherein the worker role component is further configured to select a first cloud storage partition for storage of industrial data associated with one of the data queues based on the behavior assembly data.

10. The system of claim 8, wherein the worker role component is further configured to process the industrial data according to the respective processing priorities, and wherein the respective processing priorities are defined by the behavior assembly data.

11. The system of claim 8, wherein the executable components further comprise a manifest that maintains mapping information defining a mapping between behavior assembly data and data types.

12. The system of claim 11, wherein the behavior assembly data comprises first behavior assembly data, and the receiving component is further configured to receive second behavior assembly data from the cloud agent device defining a processing preference for a data type, to create a new data queue corresponding to the second behavior assembly data in response to receipt of the second behavior assembly, and to store the second behavior assembly data in the manifest, wherein the processing preference comprises at least an upload frequency at which industrial data corresponding to the data type is to be uploaded from the cloud agent device to the receiving component.

13. The system of claim 12, wherein the receiving component is further configured to at least one of create a second cloud storage partition for the data type or expand an existing cloud storage partition in accordance with the second behavior assembly data in response to receipt of the second behavior assembly data.

14. The system of claim 7, wherein the header includes a field that specifies one of the data queues and a field for at least one of a customer identifier, a site identifier a virtual support engineer identifier, a data priority, a message type, or a process identifier.

15. The system of claim 7, wherein the live data queue is assigned a higher processing priority than the historical data queue.

16. The system of claim 10, wherein the executable components further comprise a notification component configured to send a notification directed to a client device based on a result of an analysis performed by the worker role component on at least a subset of the industrial data.

17. A method for storing and processing industrial data, comprising:
creating, by a system comprising at least one processor, a set of message queues on a cloud platform, wherein the set of message queues comprise at least a historical data queue for processing of time-series record data, a live data queue for processing of real-time monitored data, and an alarms queue for processing of alarm data;
associating, by the system, the set of message queues with respective processing priorities, wherein associating comprises assigning a highest processing priority to the alarm queue;
receiving, by the system at the cloud platform, data packets from a cloud agent device, wherein the data packets respectively comprise industrial data and a header for the industrial data;
classifying, by the system, the data packets based on the header, including classifying the data packets according to time-series record data, real-time monitored data, and alarm data; and
assigning, by the system, the industrial data associated with the respective data packets to selected message queues of the set of message queues in accordance with the classifying.

18. The method of claim 17, further comprising processing, by the system, the data packets on the cloud platform based on behavior assembly data associated with the respective message queues.

19. The method of claim 18, further comprising storing, by the system, at least a subset of the industrial data in a first cloud storage partition selected based on the behavior assembly data.

20. The method of claim 17, further comprising:
receiving, by the system at the cloud platform, second behavior assembly data from the cloud agent device that defines a processing preference for a data type;
creating, by the system on the cloud platform, a new message queue corresponding to the second behavior assembly data in response to the receiving the second behavior assembly data; and
storing, by the system, the second behavior assembly data in a manifest that maintains mapping definitions that define respective mappings between behavior assembly data and data types.