Patent Grant
10223327
The present disclosure relates generally to process plants and to process control systems, and more particularly, to devices that support big data in process plants and process control systems.
Distributed process control systems, like those used in chemical, petroleum or other process plants, typically include one or more process controllers communicatively coupled to one or more field devices via analog, digital or combined analog/digital buses, or via a wireless communication link or network. The field devices, which may be, for example, valves, valve positioners, switches and transmitters (e.g., temperature, pressure, level and flow rate sensors), are located within the process environment and generally perform physical or process control functions such as opening or closing valves, measuring process parameters, etc. to control one or more process executing within the process plant or system. Smart field devices, such as the field devices conforming to the well-known Fieldbus protocol may also perform control calculations, alarming functions, and other control functions commonly implemented within the controller. The process controllers, which are also typically located within the plant environment, receive signals indicative of process measurements made by the field devices and/or other information pertaining to the field devices and execute a controller application that runs, for example, different control modules which make process control decisions, generate control signals based on the received information and coordinate with the control modules or blocks being performed in the field devices, such as HART®, WirelessHART®, and FOUNDATION® Fieldbus field devices. The control modules in the controller send the control signals over the communication lines or links to the field devices to thereby control the operation of at least a portion of the process plant or system.
Information from the field devices and the controller is usually made available over a data highway to one or more other hardware devices, such as operator workstations, personal computers or computing devices, data historians, report generators, centralized databases, or other centralized administrative computing devices that are typically placed in control rooms or other locations away from the harsher plant environment. Each of these hardware devices typically is centralized across the process plant or across a portion of the process plant. These hardware devices run applications that may, for example, enable an operator to perform functions with respect to controlling a process and/or operating the process plant, such as changing settings of the process control routine, modifying the operation of the control modules within the controllers or the field devices, viewing the current state of the process, viewing alarms generated by field devices and controllers, simulating the operation of the process for the purpose of training personnel or testing the process control software, keeping and updating a configuration database, etc. The data highway utilized by the hardware devices, controllers and field devices may include a wired communication path, a wireless communication path, or a combination of wired and wireless communication paths.
As an example, the DeltaV™ control system, sold by Emerson Process Management, includes multiple applications stored within and executed by different devices located at diverse places within a process plant. A configuration application, which resides in one or more workstations or computing devices, enables users to create or change process control modules and download these process control modules via a data highway to dedicated distributed controllers. Typically, these control modules are made up of communicatively interconnected function blocks, which are objects in an object oriented programming protocol that perform functions within the control scheme based on inputs thereto and that provide outputs to other function blocks within the control scheme. The configuration application may also allow a configuration designer to create or change operator interfaces which are used by a viewing application to display data to an operator and to enable the operator to change settings, such as set points, within the process control routines. Each dedicated controller and, in some cases, one or more field devices, stores and executes a respective controller application that runs the control modules assigned and downloaded thereto to implement actual process control functionality. The viewing applications, which may be executed on one or more operator workstations (or on one or more remote computing devices in communicative connection with the operator workstations and the data highway), receive data from the controller application via the data highway and display this data to process control system designers, operators, or users using the user interfaces, and may provide any of a number of different views, such as an operator's view, an engineer's view, a technician's view, etc. A data historian application is typically stored in and executed by a data historian device that collects and stores some or all of the data provided across the data highway while a configuration database application may run in a still further computer attached to the data highway to store the current process control routine configuration and data associated therewith. Alternatively, the configuration database may be located in the same workstation as the configuration application.
The architecture of currently known process control plants and process control systems is strongly influenced by limited controller and device memory, communications bandwidth and controller and device processor capability. For example, in currently known process control system architectures, the use of dynamic and static non-volatile memory in the controller is usually minimized or, at the least, managed carefully. As a result, during system configuration (e.g., a priori), a user typically must choose which data in the controller is to be archived or saved, the frequency at which it will be saved, and whether or not compression is used, and the controller is accordingly configured with this limited set of data rules. Consequently, data which could be useful in troubleshooting and process analysis is often not archived, and if it is collected, the useful information may have been lost due to data compression.
Additionally, to minimize controller memory usage in currently known process control systems, selected data that is to be archived or saved (as indicated by the configuration of the controller) is reported to the workstation or computing device for storage at an appropriate data historian or data silo. The current techniques used to report the data poorly utilizes communication resources and induces excessive controller loading. Additionally, due to the time delays in communication and sampling at the historian or silo, the data collection and time stamping is often out of sync with the actual process.
Similarly, in batch process control systems, to minimize controller memory usage, batch recipes and snapshots of controller configuration typically remain stored at a centralized administrative computing device or location (e.g., at a data silo or historian), and are only transferred to a controller when needed. Such a strategy introduces significant burst loads in the controller and in communications between the workstation or centralized administrative computing device and the controller.
Furthermore, the capability and performance limitations of relational databases of currently known process control systems, combined with the previous high cost of disk storage, play a large part in structuring data into independent entities or silos to meet the objectives of specific applications. For example, within the DeltaV™ system, the archiving of process models, continuous historical data, and batch and event data are saved in three different application databases or silos of data. Each silo has a different interface to access the data stored therein.
Structuring data in this manner creates a barrier in the way that historized data is accessed and used. For example, the root cause of variations in product quality may be associated with data in more than of these data silos. However, because of the different file structures of the silos, it is not possible to provide tools that allow this data to be quickly and easily accessed for analysis. Further, audit or synchronizing functions must be performed to ensure that data across different silos is consistent.
The limitations of currently known process plants and process control system discussed above and other limitations may undesirably manifest themselves in the operation and optimization of process plants or process control systems, for instance, during plant operations, trouble shooting, and/or predictive modeling. For example, such limitations force cumbersome and lengthy work flows that must be performed in order to obtain data for troubleshooting and generating updated models. Additionally, the obtained data may be inaccurate due to data compression, insufficient bandwidth, or shifted time stamps.
“Big data” generally refers to a collection of one or more data sets that are so large or complex that traditional database management tools and/or data processing applications (e.g., relational databases and desktop statistic packages) are not able to manage the data sets within a tolerable amount of time. Typically, applications that use big data are transactional and end-user directed or focused. For example, web search engines, social media applications, marketing applications and retail applications may use and manipulate big data. Big data may be supported by a distributed database which allows the parallel processing capability of modern multi-process, multi-core servers to be fully utilized.
A device that supports big data in a process control system or plant is configured to collect all (or almost all) of the data that is observed by the device (e.g., data that is directly generated by, created by, or directly received at the device). As such, the device may include a processor that has multiple processing elements (e.g., a multi-core processor) and/or a high density memory or cache. In an embodiment, the collected data may be stored in the cache of the device. The device is further configured to cause the collected data to be transmitted to a unitary, logical data storage area for historization or long-term storage as big data, for example, by streaming the data. The unitary, logical data storage area is configured to store, using a common format, multiple types of data that are generated or created by or related to the process control system, the process plant, and to one or more processes being controlled by the process plant. For example, the unitary, logical data storage area may store configuration data, continuous data, event data, calculated data, plant data, data indicative of a user action, network management data, and data provided by or to systems external to the process control system or plant. In an embodiment, the processor of the device operates to collect all (or almost all) data that is observed by the device, and to stream the collected data to be stored in the unitary, logical data storage area by using a process control system big data network. The device may be a node of the process control system big data network.
The process control system big data network provides an infrastructure for supporting large scale data mining and data analytics of process data and other types of data collected by device that support big data in process control environments. In an embodiment, the process control big data network or system includes a plurality of nodes to collect and store all (or almost all) data that is generated, created, received, and/or observed by devices included in and associated with the process control system or plant. The devices described in the present application may be nodes of such a process control system big data network. Another node of the process control big data network may be a process control system big data apparatus. The process control system big data apparatus may include the unitary, logical data storage area to which the devices cause collected data to be transmitted for storage or historization.
Unlike prior art process control systems, the identity of data that is to be collected at the devices or the nodes of the process control system big data network need not be defined or configured into the devices or nodes a priori. Further, the rate at which data, such as dynamic measurement and control data and/or various other types of dynamic and/or static data, is collected at and transmitted from the devices or nodes also need not be configured, selected, or defined a priori. Instead, a device that supports process control big data may automatically collect or capture data that is generated by, created by, received at, or otherwise observed by the device at the rate at which the data is generated, created, received or observed, and may cause the collected data to be delivered in high fidelity (e.g., without using lossy data compression or any other techniques that may cause loss of original information) to the process control system big data apparatus to be stored (and, optionally, delivered to other nodes or devices).
In an embodiment, a device that supports big data in a process control system or plant is a process control device configured to control a process in the process plant. The process control device may be, for example, a field device configured to perform a physical function to control the process; a controller configured to receive an input and generate, based on the input and a control routine, an output to control the process; or an input/output (I/O) device disposed between and communicatively connecting the controller and one or more field devices. The process control device may include a processor having multiple processing elements and/or a cache configured to store collected data. Typically, the collected data corresponds to the process plant or to the process controlled in the process plant, and includes data that is directly generated by the process control device, created by the process control device, and/or data that is directly received by the process control device. The process control device also includes an interface to a communications network via which the collected data is transmitted for storage in the unitary, logical data storage area. In some embodiments, a particular processing element of the processor of the device may be exclusively designated to cache and cause the collected data to be transmitted to a unitary, logical data storage area for historization.
A method of delivering data (e.g., big data) in a process control system or plant uses a device that is communicatively coupled to a communications network of the process plant. The method may include collecting data at the device, storing the collected data in a cache of the device, and causing at least a portion of the collected data to be transmitted for storage in a unitary, logical data storage area. The unitary, logical data storage area is configured to store, using a common format, multiple types of data from a set of types of data corresponding to the process plant or the process controlled by the process plant, for example, and the set of types of data may include continuous data, event data, measurement data, batch data, calculated data, configuration data, and other types of data. Typically, the data collected at the device corresponds to the process plant or to a process controlled by the process plant, and includes data that is directly generated by the device, data that is created by the device, and/or data that is directly received at the device. A type of the device is one from a set of device types including a field device and a controller. In some embodiments, the set of device types may include other device types, such as user interface devices, network management devices, historian devices, and/or other types of devices. In an embodiment, all data that is observed by the device is collected and caused to be stored at the unitary, logical data storage area.
In an embodiment, devices supporting big data in a process control plant or system are nodes of a process control system big data network corresponding to the process control plant or system. The plurality of devices or nodes may include process control devices, network management devices, user interface devices, gateway device, historian devices, and/or other types of devices. Each node or device may be configured to collect respective first data that the device directly generates or directly receives, and may temporarily store the collected data in a cache. Each node or device may cause at least a portion of the collected data to be transmitted, via the communications network, for storage in a unitary, logical data storage area. Moreover, at least one node or device is further configured to receive second data that was directly generated by, created by, or directly received at another node of the plurality of nodes, and to cause the second data to be forwarded for storage in the unitary, logical data storage area. The communications network is configured to deliver data to be stored in the unitary, logical data storage area, and the unitary, logical data storage area is configured to store multiple types of data from a set of data types corresponding to the process plant or a process controlled by the process plant in a common format. The set of data types may include, for example, continuous data, event data, measurement data, batch data, calculated data, and configuration data.
By using such devices and techniques to support big data in a process control system or plant, a process control system big data system is able to provide sophisticated data and trending analyses for any portion of the stored or historized data. For example, the process control big data system is able to provide automatic data analysis across process data (that, in prior art process control systems, is contained in different database silos) without requiring any a priori configuration and without requiring any translation or conversion. Based on the analyses, the process control system big data system is able to automatically provide in-depth knowledge discovery, and may suggest changes to or additional entities for the process control system. Additionally or alternatively, the process control system big data system may perform actions (e.g., prescriptive, predictive, or both) based on the knowledge discovery. The process control system big data system also is enable and assist users in performing manual knowledge discovery, and in planning, configuring, operating, maintaining, and optimizing the process plant and resources associated therewith.
Knowledge discovery and big data techniques within a process control plant or environment are inherently different than traditional big data techniques. Typically, traditional big data applications are singularly transactional, end-user directed, and do not have strict time requirements or dependencies. For example, a web retailer collects big data pertaining to browsed products, purchased products, and customer profiles, and uses this collected data to tailor advertising and up-sell suggestions for individual customers as they navigate the retailer's web site. If a particular retail transaction (e.g., a particular data point) is inadvertently omitted from the retailer's big data analysis, the effect of its omission is negligible, especially when the number of analyzed data points is very large. In the worst case, an advertisement or up-sell suggestion may not be as closely tailored to a particular customer as could have been if the omitted data point had been included in the retailer's big data analysis.
In process plant and process control environments, though, the dimension of time and the presence or omission of particular data points is critical. For example, if a particular data value is not delivered to a recipient component of the process plant within a certain time interval, a process may become uncontrolled, which may result in a fire, explosion, loss of equipment, and/or loss of human life. Furthermore, multiple and/or complex time-based relationships between different components, entities, and/or processes operating within the process plant and/or external to the process plant may affect operating efficiency, product quality, and/or plant safety. The knowledge discovery provided by the process control system big data techniques described herein may allow such time-based relationships to be discovered and utilized, thus enabling a more efficient and safe process plant that may produce a higher quality product.
Further, by having a processor having multiple processing elements and expanded memory storage in devices, the devices or nodes that support big data in a process control plant or system may be able to overcome many of the performance limitations associated with currently known devices such as memory and processor capabilities. As a result, the devices or nodes may be able to automatically capture, store and archive all types of data including data that may be useful for troubleshooting and process analysis. As well, the devices or nodes in the process control system big data network or system may be able to efficiently utilize communication resources to reduce excessive communication loading and/or time delays in communication and sampling at historians or silos (e.g., loading of controllers, transferring of batch recipes, etc.). As such, all data collection, time stamping, and transmission are carried out in sync with the actual process.
Any type of data related to the process control system 10 may be collected at the devices 108 and stored at the process control system big data appliance 102 as big data. In an embodiment, process data may be collected and stored. For example, real-time process data such as continuous, batch, measurement and event data that is generated while a process is being controlled in the process plant 10 (and, in some cases, is indicative of an effect of a real-time execution of the process) may be collected and stored. Process definition, arrangement or set-up data such as configuration data and/or batch recipe data may be collected and stored. Data corresponding to the configuration, execution and results of process diagnostics may be collected and stored. Other types of process data may also be collected and stored.
Further, data highway traffic and network management data related to the backbone 105 and of various other communications networks of the process plant 10 may be collected at the devices 108 and stored at the appliance 102. User-related data such as data related to user traffic, login attempts, queries and instructions may be collected and stored. Text data (e.g., logs, operating procedures, manuals, etc.), spatial data (e.g., location-based data) and multi-media data (e.g., closed circuit TV, video clips, etc.) may be collected and stored.
In some scenarios, data that is related to the process plant 10 (e.g., to physical equipment included in the process plant 10 such as machines and devices) but that may not be generated by applications that directly configure, control, or diagnose a process may be collected at the devices 108 and stored at the appliance 102. In an embodiment, data that is created by devices and/or equipment is collected and stored. For example, vibration data and steam trap data is collected and stored. Plant safety data may be collected and stored. Other examples of such plant data include data indicative of a value of a parameter corresponding to plant safety (e.g., corrosion data, gas detection data, etc.), or data indicative of an event corresponding to plant safety. Data corresponding to the health of machines, plant equipment and/or devices may be collected and stored, e.g., data that is created by the devices and/or machines that is used for diagnostic or prognostic purposes. For example, equipment data (e.g., pump health data determined based on vibration data and other data) is collected and stored. Data corresponding to the configuration, execution and results of equipment, machine, and/or device diagnostics may be collected and stored. Further, created or calculated data that is useful for diagnostics and prognostics may be collected and stored.
In some embodiments, data generated by or transmitted to entities external to the process plant 10 may be collected at the devices 108 and stored at the appliance 102, such as data related to costs of raw materials, expected arrival times of parts or equipment, weather data, and other external data. In an embodiment, all data that is generated by, created by, received at, or otherwise observed by all devices or nodes 108 that are communicatively connected to the network backbone 105 is collected and caused to be stored at the process control system big data appliance 102 as big data. In some situations, at least some of the collected data is compressed prior to transferring the collected data to the big data appliance 102.
Various types of data may be collected and caused to be stored at the process control system big data appliance 102 as big data. For example, in some embodiments, dynamic measurement and control data is automatically communicated from the devices 108 for collection at the appliance 102. Examples of dynamic measurement and control data may include data specifying changes in a process operation, data specifying changes in operating parameters such as setpoints, records of process and hardware alarms and events such as downloads or communication failures, etc. In any event, in these embodiments, all types of measurement and control data are captured in the devices 108 and automatically communicated to the process control system big data appliance 102 for storage as big data. In addition, static data such as controller configurations, batch recipes, alarms and events may be automatically communicated by default when a change is detected or when a controller or other entity is initially added to the big data network 100.
Moreover, in some scenarios, at least some static metadata that describes or identifies dynamic control and measurement data is sent to the big data appliance 102 when a change in the metadata is detected. For example, if a change is made in the controller configuration that impacts the measurement and control data in modules or units that must be sent by the controller, then an update of the associated metadata is automatically sent by the controller to the big data appliance 102. In some situations, parameters associated with the special modules used for buffering data from external systems or sources (e.g., weather forecasts, public events, company decisions, etc.) are automatically communicated by default to the big data appliance 102. Additionally or alternatively, surveillance data and/or other types of monitoring data may be automatically communicated to the big data appliance 102.
Further, in some embodiments, added parameters created by end users are automatically communicated to the big data appliance 102 for storage as big data. For example, an end user may create a special calculation in a module or may add a parameter to a unit that needs to be collected, or the end user may want to collect a standard controller diagnostic parameter that is not communicated by default. Parameters that the end user optionally configures to be collected in the big data appliance 102 may be communicated in the same manner as the default parameters.
The process control system big data network 100 may include a process control system big data studio 109 configured to provide a primary interface into the process control system big data network 100 for configuration and data exploration, e.g., a user interface or an interface for use by other applications. The process control system big data studio 109 may be connected to the big data appliance 102 via the process control system big data network backbone 105, or may be directly connected to the process control system big data appliance 102.
The plurality of devices or nodes 108 of the process control big data network 100 may include several different groups of devices or nodes 110-115 that support big data in process control systems or plants. A first group of devices or nodes 110, referred to herein as “provider nodes 110” or “provider devices 110,” may include one or more nodes or devices that generate, route, and/or receive process control data to enable processes to be controlled in real-time in the process plant environment 10. Examples of provider devices or nodes 110 include devices whose primary function is directed to generating and/or operating on process control data to control a process, e.g., wired and wireless field devices, controllers, or input/output (I/O devices). Other examples of provider devices 110 include devices whose primary function is to provide access to or routes through one or more communications networks of the process control system (of which the process control big network 100 is one), e.g., access points, routers, interfaces to wired control busses, gateways to wireless communications networks, gateways to external networks or systems, and other such routing and networking devices. Still other examples of provider devices 110 include devices whose primary function is to temporarily store process data and other related data that is accumulated throughout the process control system 10 and to cause the temporarily stored data to be transmitted for historization at the process control system big data appliance 102, e.g., historian devices or historian nodes.
At least one of the provider devices 110 may be communicatively connected to the process control big data network backbone 105 in a direct manner. In an embodiment, at least one of the provider devices 110 is communicatively connected to the backbone 105 in an indirect manner. For example, a wireless field device is communicatively connected to the backbone 105 via a router, and access point, and a wireless gateway. Typically, provider devices or nodes 110 do not have an integral user interface, although some of the provider devices 100 may have the capability to be in communicative connection with a user computing device or user interface, e.g., by communicating over a wired or wireless communication link, or by plugging a user interface device into a port of the provider device 110.
A second group of devices or nodes 112 that support big data in process control systems or plants is referred to herein as “user interface nodes 112” or “user interface devices 112.” The second group of devices 112 includes one or more nodes or devices that each have an integral user interface via which a user or operator may interact with the process control system or process plant 10 to perform activities related to the process plant 10 (e.g., configure, view, monitor, test, analyze, diagnose, order, plan, schedule, annotate, and/or other activities). Examples of these user interface nodes or devices 112 include mobile or stationary computing devices, workstations, handheld devices, tablets, surface computing devices, and any other computing device having a processor, a memory, and an integral user interface. Integrated user interfaces may include a screen, a keyboard, keypad, mouse, buttons, touch screen, touch pad, biometric interface, speakers and microphones, cameras, and/or any other user interface technology. Each user interface node 112 may include one or more integrated user interfaces. User interface nodes 112 may include a direct connection to the process control big data network backbone 105, or may include in indirect connection to the backbone 105, e.g., via an access point or a gateway. User interface nodes 112 may communicatively connect to the process control system big data network backbone 105 in a wired manner and/or in a wireless manner. In some embodiments, a user interface node 112 may connect to the network backbone 105 in an ad-hoc manner.
Of course, the plurality of devices or nodes 108 supporting big data in process control plants and systems is not limited to only provider nodes 110 and user interface nodes 112. One or more other types of devices or nodes 115 may also be included in the plurality of devices or nodes 108. For example, a node 115 of a system that is external to the process plant 10 (e.g., a lab system or a materials handling system) may be communicatively connected to the network backbone 105 of the system 100. A node or device 115 may be communicatively connected to the backbone 105 via a direct or an indirect connection, and a node or device 115 may be communicatively connected to the backbone 105 via a wired or a wireless connection. In some embodiments, the group of other devices or nodes 115 may be omitted from the process control system big data network 100.
In an embodiment, at least some of the devices or nodes 108 supporting big data in process control plants or systems may include an integrated firewall. Further, any number of the devices 108 (e.g., zero devices, one device, or more than one device) may each include respective memory storage (denoted in
Any number of the devices 108 (for example, zero devices, one device, or more than one device) may each include respective hardware having multiple processing elements, for example, a processor having multiple processing elements such as multiple cores or other co-processing technologies (e.g., quantum, cell, chemical, photonic, bio-chemical, biological processing technologies). The processors having multiple processing elements or co-processing capabilities are denoted in the
At least some of the devices 108 may designate at least one of its multiple processing elements of its respective processor PMCX for caching real-time data at the node and, optionally, for causing the cached data to be transmitted for storage at the process control system big data appliance 102. In some embodiments, the one or more designated processing elements for caching and/or transmitting real-time data may be exclusively designated as such (e.g., the one or more designated processing elements may perform no other processing except processing related to caching and/or transmitting big data observed by the device 108). At least some of the devices 108 may designate at least one of its processing elements to perform operations to control a process in the process plant 10. In an embodiment, one or more processing elements may be designated exclusively for performing operations to control a process, and may not be used to cache and transmit big data. It is understood that different types or technologies of processors PMCX having different multi-processing element technologies may be utilized across the set of devices 108, or across a subset the set of devices 108. In an embodiment of the process control system big data network 100, all of the devices 110, 112 and any number of the devices 115 may include some type of processor PMCX that utilizes multi-processing element technology.
While
Examples of real-time data that may be collected (and in some cases, cached) by provider nodes or devices 110 may include measurement data, configuration data, batch data, event data, and/or continuous data. For instance, real-time data corresponding to configurations, batch recipes, setpoints, outputs, rates, control actions, diagnostics, health of the device or of other devices, alarms, events and/or changes thereto may be collected. Other examples of real-time data may include process models, statistics, status data, and network and plant management data.
Examples of real-time data that may be collected (and in some cases, cached) by user interface nodes or devices 112 may include, for example, user logins, user queries, data captured by a user (e.g., by camera, audio, or video recording device), user commands, creation, modification or deletion of files, a physical or spatial location of a user interface node or device, results of a diagnostic or test performed by the user interface device 112, and other actions or activities initiated by or related to a user interacting with a user interface node 112.
Collected data may be dynamic or static data. Collected data may include, for example, database data, configuration data, batch data, streaming data, and/or transactional data. Generally, any data that a device 108 generates, receives, or otherwise observes may be collected (and in some cases, cached) with a corresponding time stamp or indication of a time of its generation, reception or observation by the device 108. In an embodiment, all data that a device 108 generates, receives, or observes is cached in its memory storage (e.g., high density memory storage MX) with a respective indication of a time of each data value's collection/caching (e.g., a timestamp).
In an embodiment, each of the devices 110, 112 (and, optionally, at least one of the other devices 115) is configured to automatically collect (and in some cases, cache) real-time data, and to cause the collected/cached data to be delivered to the big data appliance 102 and/or to other devices 108 without requiring lossy data compression, data sub-sampling, or configuring the node for data collection purposes. Thus, the devices 110, 112 (and, optionally, at least one of the other devices 115) of the process control big data system 100 may automatically collect all data (e.g., measurement and control data as well as various other types of data) that is generated by, created by, received at, or obtained by the device at a rate at which the data is generated, created, received or obtained, and may cause the collected data to be delivered in high fidelity to the process control big data appliance 102 and, optionally, to other devices 108 of the network 100.
Referring again to
The big data network backbone 105 may support one or more suitable routing protocols, e.g., protocols included in the Internet Protocol (IP) suite (e.g., UPD (User Datagram Protocol), TCP (Transmission Control Protocol), Ethernet, etc.), or other suitable routing protocols. In an embodiment, at least some of the devices 108 utilize a streaming protocol such as the Stream Control Transmission Protocol (SCTP) to stream cached data from the devices 108 to the process control big data appliance 102 via the network backbone 105. Typically, each device or node 108 included in the process data big data network 100 may support at least an application layer (and, for some devices, additional layers) of the routing protocol(s) supported by the backbone 105. In an embodiment, each device or node 108 is uniquely identified within the process control system big data network 100, e.g., by a unique network address.
In an embodiment, at least a portion of the process control system big data network 100 may be an ad-hoc network. As such, at least some of the devices 108 may connect to the network backbone 105 (or to another node of the network 100) in an ad-hoc manner.
Continuing with
The process control system big data storage area 120 may comprise multiple physical data drives or storage entities, such as RAID (Redundant Array of Independent Disks) storage, cloud storage, or any other suitable data storage technology that is suitable for data bank or data center storage. However, to the devices 108 of the network 100, the data storage area 120 has the appearance of a single or unitary logical data storage area or entity. As such, the data storage 120 may be viewed as a centralized big data storage area 120 for the process control big data network 100 or for the process plant 10. In some embodiments, a single logical centralized data storage area 120 services multiple process plants (e.g., the process plant 10 and another process plant). For example, a centralized data storage area 120 services several refineries of an energy company. In an embodiment, the centralized data storage area 120 is directly connected to the backbone 105. In some embodiments, the centralized data storage area 120 is connected to the backbone 105 via at least one high-bandwidth communication link. In an embodiment, the centralized data storage area 120 includes an integral firewall.
The structure of the unitary, logical data storage area 120 supports the storage of all process control system and plant related data, in an embodiment. For example, each entry, data point, or observation stored in the data storage area 120 may include an indication of the identity of the data (e.g., source, device, tag, location, etc.), a content of the data (e.g., measurement, value, etc.), and a timestamp indicating a time at which the data was collected, generated, created, received, or observed. As such, these entries, data points, or observations are referred to herein as “time-series data.” The data may be stored in the data storage area 120 using a common format including a schema that supports scalable storage, streamed data, and low-latency queries, for example.
In an embodiment, the schema includes storing multiple observations in each row, and using a row-key with a custom hash to filter the data in the row. The hash is based on the timestamp and a tag, in an embodiment. In an example, the hash is a rounded value of the timestamp, and the tag corresponds to an event or an entity of or related to the process control system. In an embodiment, metadata corresponding to each row or to a group of rows is also stored in the data storage area 120, either integrally with the time-series data or separately from the time-series data. For example, the metadata may be stored in a schema-less manner separately from the time-series data.
In an embodiment, the schema used for storing data at the appliance data storage 120 is also utilized for storing data in the cache MX of at least one of the devices 108. Accordingly, in this embodiment, the schema is maintained when data is transmitted from the local storage areas MX of the devices 108 across the backbone 105 to the process control system big data appliance data storage 120.
In addition to the data storage 120, the process control system big data appliance 102 may further include one or more appliance data receivers 122, each of which is configured to receive data packets from the backbone 105, process the data packets to retrieve the substantive data and timestamp carried therein, and store the substantive data and timestamp in the data storage area 120. The appliance data receivers 122 may reside on a plurality of computing devices or switches, for example. In an embodiment, multiple appliance data receivers 122 (and/or multiple instances of at least one data receiver 122) may operate in parallel on multiple data packets.
In embodiments in which the received data packets include the schema utilized by the process control big data appliance data storage area 120, the appliance data receivers 122 merely populate additional entries or observations of the data storage area 120 with the schematic information (and, may optionally store corresponding metadata, if desired). In embodiments in which the received data packets do not include the schema utilized by the process control big data appliance data storage area 120, the appliance data receivers 122 may decode the packets and populate time-series data observations or data points of the process control big data appliance data storage area 120 (and, optionally corresponding metadata) accordingly.
Additionally, the process control system big data appliance 102 may include one or more appliance request servicers 125, each of which is configured to access time-series data and/or metadata stored in the process control system big data appliance storage 120, e.g., per the request of a requesting entity or application. The appliance request servicers 125 may reside on a plurality of computing devices or switches, for example. In an embodiment, at least some of the appliance request servicers 125 and the appliance data receivers 122 reside on the same computing device or devices (e.g., on an integral device), or are included in an integral application. In some scenarios, the appliance request servicers 125 may request data that has been retrieved from the big data application storage 120 and that has been cleaned to remove noise and inconsistent data. In some scenarios, the appliance request servicers 125 may perform data cleaning and/or data integration on at least some of the data retrieved from the big data application data storage 120.
In an embodiment, multiple appliance request servicers 125 (and/or multiple instances of at least one appliance request servicer 125) may operate in parallel on multiple requests from multiple requesting entities or applications. In an embodiment, a single appliance request servicer 125 may service multiple requests, such as multiple requests from a single entity or application, or multiple requests from different instances of an application.
A detailed block diagram illustrating example provider devices 110 that support big data in process control systems or plants is shown in
As previously discussed, the provider devices 110 may include devices whose main function is to automatically generate and/or receive process control data that is used to perform functions to control a process in real-time in the process plant environment 10, such as process controllers, field devices and I/O devices. In a process plant environment 10, process controllers receive signals indicative of process measurements made by field devices, process this information to implement a control routine, and generate control signals that are sent over wired or wireless communication links to other field devices to control the operation of a process in the plant 10. Typically, at least one field device performs a physical function (e.g., opening or closing a valve, increase or decrease a temperature, etc.) to control the operation of a process, and some types of field devices may communicate with controllers using I/O devices. Process controllers, field devices, and I/O devices may be wired or wireless, and any number and combination of wired and wireless process controllers, field devices and I/O devices may be nodes 110 of the process control big data network 100 that support big data.
For example,
The controller 11, which may be, by way of example, the DeltaV™ controller sold by Emerson Process Management, may operate to implement a batch process or a continuous process using at least some of the field devices 15-22 and 40-46. In an embodiment, in addition to being communicatively connected to the process control big data network backbone 105, the controller 11 may also be communicatively connected to at least some of the field devices 15-22 and 40-46 using any desired hardware and software associated with, for example, standard 4-20 mA devices, I/O cards 26, 28, and/or any smart communication protocol such as the FOUNDATION® Fieldbus protocol, the HART® protocol, the WirelessHART® protocol, etc. In an embodiment, the controller 11 may be communicatively connected with at least some of the field devices 15-22 and 40-46 using the big data network backbone 105. In
The controller 11 of
In some embodiments, the controller 11 implements a control strategy using what are commonly referred to as function blocks, wherein each function block is an object or other part (e.g., a subroutine) of an overall control routine and operates in conjunction with other function blocks (via communications called links) to implement process control loops within the process control system 10. Control based function blocks typically perform one of an input function, such as that associated with a transmitter, a sensor or other process parameter measurement device, a control function, such as that associated with a control routine that performs PID, fuzzy logic, etc. control, or an output function which controls the operation of some device, such as a valve, to perform some physical function within the process control system 10. Of course, hybrid and other types of function blocks exist. Function blocks may be stored in and executed by the controller 11, which is typically the case when these function blocks are used for, or are associated with standard 4-20 ma devices and some types of smart field devices such as HART devices, or may be stored in and implemented by the field devices themselves, which can be the case with Fieldbus devices. The controller 11 may include one or more control routines 38 that may implement one or more control loops. Each control loop is typically referred to as a control module, and may be performed by executing one or more of the function blocks.
Other examples of devices 110 that support big data in the process plant or system 10 are the wired field devices 15-22 and the I/O cards 26, 28 shown in
The wireless field devices 40-46 shown in
The wireless gateway 35 is another example of a provider device 110 that supports big data in the process control plant or system 10. The wireless gateway 35 may provide access to various wireless devices 40-58 of a wireless communications network 70. In particular, the wireless gateway 35 provides communicative coupling between the wireless devices 40-58, the wired devices 11-28, and/or other nodes or devices 108 of the process control big data network 100 (including the controller 11 of
The wireless gateway 35 provides communicative coupling, in some cases, by the routing, buffering, and timing services to lower layers of the wired and wireless protocol stacks (e.g., address conversion, routing, packet segmentation, prioritization, etc.) while tunneling a shared layer or layers of the wired and wireless protocol stacks. In other cases, the wireless gateway 35 may translate commands between wired and wireless protocols that do not share any protocol layers. In addition to protocol and command conversion, the wireless gateway 35 may provide synchronized clocking used by time slots and superframes (sets of communication time slots spaced equally in time) of a scheduling scheme associated with the wireless protocol implemented in the wireless network 70. Furthermore, the wireless gateway 35 may provide network management and administrative functions for the wireless network 70, such as resource management, performance adjustments, network fault mitigation, monitoring traffic, security, and the like. The wireless gateway 35 may be a node 110 of the process control system big data network 100.
Similar to the wired field devices 15-22, the wireless field devices 40-46 of the wireless network 70 may perform physical control functions within the process plant 10, e.g., opening or closing valves or take measurements of process parameters. The wireless field devices 40-46, however, are configured to communicate using the wireless protocol of the network 70. As such, the wireless field devices 40-46, the wireless gateway 35, and other wireless nodes 52-58 of the wireless network 70 are producers and consumers of wireless communication packets.
In some scenarios, the wireless network 70 may include non-wireless devices. For example, a field device 48 of
Furthermore, the wireless network 70 may include one or more network access points 55a, 55b, which may be separate physical devices in wired communication with the wireless gateway 35 or may be provided with the wireless gateway 35 as an integral device. In
Accordingly,
The devices 110 of the process control big data network 100 that support big data, though, may also include other devices that communicate using other wireless protocols. In
The provider devices or nodes 110 that support big data in the process plant or system 10 may include one or more gateways 75, 78 to systems that are external to the immediate process control system 10. Typically, such systems are customers or suppliers of information generated or operated on by the process control system 10. For example, a plant gateway node 75 may communicatively connect the immediate process plant 10 (having its own respective process control big data network backbone 105) with another process plant having its own respective process control big data network backbone. In an embodiment, a single process control big data network backbone 105 may service multiple process plants or process control environments. The network 105 may support one or more process control system big data appliances 102 that are remotely located from the physical process plants, and each big data appliance 102 may service one or more process plants.
In another example, a plant gateway node 75 may communicatively connect the immediate process plant 10 to a legacy or prior art process plant that does not include a process control big data network 100 or backbone 105. In this example, the plant gateway node 75 may convert or translate messages between a protocol utilized by the process control big data backbone 105 of the plant 10 and a different protocol utilized by the legacy system (e.g., Ethernet, Profibus, Fieldbus, DeviceNet, etc.).
The provider devices or nodes 110 that support big data in the process plant or system 10 may include one or more external system gateway nodes 78 to communicatively connect the process control big data network 100 with the network of an external public or private system, such as a laboratory system (e.g., Laboratory Information Management System or LIMS), an operator rounds database, a materials handling system, a maintenance management system, a product inventory control system, a production scheduling system, a weather data system, a shipping and handling system, a packaging system, the Internet, another provider's process control system, or other external systems.
Although
As previously discussed, one or more of the provider devices or nodes 110 that support big data in the process plant or system 10 may include a respective multi-processing element processor PMCX, a respective high density memory storage MX, or both a respective multi-processing element processor PMCX and a respective high density memory storage MX (denoted in
The device 300 may be a node of a network that supports big data in a process control system, such as the process control system big data network 100 of
In an embodiment, the device 300 operates in the process plant or process control system 10 to control a process in real-time, e.g., as part of a control loop. For example, the device 300 may be connected, using a network interface 305, to a process control communications network 303 via which the device 300 may transmit signals to and/or receive signals from other devices to control a process in real-time in the process control system 10. The process control communications network 303 may be a wired or wireless communications network (e.g., the wireless network 70, a Fieldbus network, a wired HART network, etc.), or the process control communications network 303 may include both a wired and a wireless communications network. Additionally or alternatively, the device 300 may transmit and/or receive signals to control the process in real-time using the process control big data network backbone 105, e.g., via the network interface 302. In an embodiment, the network interface 302 and the process control interface 305 may be the same interface (e.g., an integral interface).
The process control interface 305 may be configured to transmit and/or receive data corresponding to a process of the process plant 10 or to a process being controlled in the process plant 10. The process control data may include measurement data (e.g., outputs, rates, etc.), configuration data (e.g., setpoints, configuration changes, etc.), batch data (e.g., batch recipes, batch conditions, etc.), event data (e.g., alarms, process control events, etc.), continuous data (e.g., parameter values, video feeds, etc.), calculated data (e.g., internal states, intermediate calculations, etc.), diagnostic data, data indicative of the health of the device 300 or of another device, and/or any other desired data. Further, the process control data may include data created by the device 300 itself, e.g., for use in purposes such as diagnostics, health monitoring, etc.
In an embodiment, the device 300 is a process controller and the process control interface 305 is used to obtain a configuration of the controller (e.g., from a workstation), and/or to obtain data that is transmitted to or received from a field device connected to the controller to control a process in real-time. For example, the controller may be connected to a wireless HART valve positioner, the valve positioner may generate process control data corresponding to a state of the valve and provide the generated data to the controller via the process control interface 305. The received data may be stored in the controller and/or may be used by the controller to perform a control function or at least a portion of a control loop. In another embodiment, the device 300 is an I/O device that provides a connection between a controller and a field device. In this embodiment, the process control interface 305 includes a field device interface to exchange process control data with the field device, and a controller interface to exchange process control data with the controller. The field device interface is connected to the controller interface so that data may be transmitted to and received from the field device to the controller via the I/O device. In yet another embodiment, the device 300 is a field device performing a physical function to control a process. For example, the device 300 may be a flow meter that measures and obtains process control data corresponding to a current measured flow via the process control interface 305, and that sends a signal corresponding to the measured flow to a controller to control a process via the interface 305. In an embodiment, the device 300 is a process control device that sends/receives diagnostic information via the interface 305 over a communication network or link 303, and causes such diagnostic information to be historized via the interface 302 and the big data backbone 105.
Although the above discussion refers to the device 300 as being a process control device operating in a control loop, the techniques and descriptions provided above apply equally to embodiments in which the device 300 is another type of device associated with the process control plant or system 10. In an example, the device 300 is a network management device such as an access point 72. The network management device observes data (e.g., bandwidth, traffic, types of data, network configuration, login identities and attempts, etc.) via the interface 305, and relays the generated data to the process control system big data network backbone 105 via the network interface 302. In yet another example, the device 300 is a user interface device 112 (e.g., a mobile device, a tablet, etc.) that is configured to allow a user or operator to interact with the process control system or process plant 10. For instance, the network interface 305 in the device 300 may be an interface to a WiFi or NFC communications link that allows the user to perform activities in the process plant 10 such as configuration, viewing, scheduling, monitoring, etc. User logins, commands, and responses may be collected via the interface 305 and transmitted to the process control system big data network backbone 105 via the network interface 302.
In an embodiment, the device 300 supporting big data in process control plants and systems causes indications of data that is directly transmitted by and/or directly received at the interface 305 to be collected at the device 300 and to be transmitted for historization in a unitary, logical data storage area corresponding to the process plant or system 10. For example, the device 300 may cause indications of all data that is transmitted and received via the interface 305 to be collected at the device 300 and to be transmitted, using the network interface 302, to the process control system big data appliance 102 for storage in the process control system big data storage area 120.
In addition to the interfaces 302, 305, the device 300 that supports big data in process control systems may include a multi-processing element processor 308 configured to execute computer-readable instructions, a memory 310, a cache 315, and, optionally, a flash memory 320. Turning first to the multi-processing element processor 308, the multi-processing element processor 308 is a computing component (e.g., an integral computing component) having two or more independent central processing units (CPU) or processing elements 308a-308n. Unlike a single processing element (e.g., single-core) processor that switches between calculations and thus can only perform one task or function at a time, the multi-processing element processor 308 is able to perform multiple tasks or functions concurrently or in parallel by allocating multiple calculations across the multiple processing elements. Tasks or functions performed by the multi-processing element processor 308 may be divided across time amongst the processing elements 308a-308n. Additionally or alternatively, at least some of the processing elements 308a-308n may be designated to perform one or more specific calculations or functions. In an embodiment, at least one processing element of the multi-processing element processor 308 is designated to cause data to be collected or captured (e.g., at the interface 305), to be stored in the cache 315, and to be transmitted from the cache 315 for storage at a centralized data storage area in the process plant environment 10 (e.g., the unitary, logical data storage area 120 in
In an embodiment, one processing element of the multi-processing element processor 308 is exclusively designated to collect and transmit data associated with the device 300 for big data storage, while another processing element of the multi-processing element processor 308 is exclusively designated to operate the device 300 for real-time process control. In an embodiment, one processing element of the multi-processor processing element 308 is designated to cause process control data to be stored in the cache 315, a second processing element of the multi-processing element processor 308 is designated to cause the cached data (or at least a portion of the cached data) to be for big data storage, and a third processing element of the multi-processing element processor 308 is designated to operate the device 300 to control a process in real-time.
The memory 310 of the device 300 includes one or more tangible, non-transitory computer-readable storage media. The memory 310 may be implemented as one or more semiconductor memories, magnetically readable memories, optically readable memories, molecular memories, cellular memories, and/or the memory 310 may utilize any other suitable tangible, non-transitory computer-readable storage media or memory storage technology. The memory 310 uses mass or high density data storage technology, in an example. The memory 310 stores one or more sets of computer-readable or computer-executable instructions that are executable by at least some of the processing elements 308a-308n of the multi-processing element processor 308 to perform collecting, caching, and/or transmitting of data to be stored at the unitary, logical data storage area.
The cache 315 may utilize data storage technology similar to that utilized by the memory 310, or may utilize different data storage technology. The cache 315 uses mass or high density data storage technology, in an example. In an embodiment, the cache 315 includes a random-access memory (RAM) configured to store data collected by the device 300 prior to the data's transmission for historization at a unitary, logical data storage area, such as the process control system big data storage area 120. The cache 315 may be included in the memory 310, and a size of the cache 315 may be selectable or configurable. Generally, the cache 315 may be written to and read from (e.g., by the multi-processing element processor 308) while the device 300 is in operation or on-line. The memories MX shown in
The cache 315 is configured to store one or more data entries. Each data entry includes a value of a datum or data point collected by the device 300, and a respective timestamp or indication of an instance of time at which the data value was generated by, created by, received at, or observed by the device 300. Both the value of the process control data and the timestamp stored in each data entry of the cache 315 may be transmitted for storage to the process control system big data storage area 120, and/or may be transmitted to other nodes and devices in the process plant environment 10. In an embodiment, a schema utilized by the cache 315 for data storage at the device 300 is included in a schema utilized by the big data storage area 120 for data storage at the process control system big data appliance 102. In another embodiment, the data in the cache 315 is stored according to a local schema of the device 300.
The device 300 may collect dynamic measurement and control data, as well as various other types of data, without requiring any user provided information that identifies or indicates a priori which data is to be collected. That is, a configuration of the device 300 excludes any indication of identities of the measurement and control data and various other types of data that is to be collected at the device 300 for eventual historization. In currently known process plants or process control systems, an operator or a user typically must configure a process control device (e.g., a controller) to capture measurement and control data by identifying which data is to be collected or saved, and, in some embodiments, by specifying the times or frequencies at which said data is to be collected or saved. The identities (and, optionally, the times/frequencies) of the data to be collected are included in the configuration of the process control device. By contrast, in a device 300 supporting process control big data, the device 300 need not be configured with the identities of the measurement and control data that is desired to be collected and the times/frequencies of its collection. Indeed, in an embodiment, all measurement and control data as well as all other types of data that is directly generated by and/or directly received at the device 300 is automatically collected.
Further, the rate at which measurement and control data and various other types of data, is collected at and/or transmitted from the device 300 also need not be configured into the device 300. That is, the rate at which data is collected and/or transmitted is excluded from a configuration of the device 300. Instead, the device 300 may automatically cause the collected measurement and control data and various other types of data to be transmitted or streamed from the device 300 for historization, in an embodiment. In an example, the device 300 is configured to stream at least some of the measurement and control and/or other types of data in real-time as the data is generated, created, received or otherwise observed by the device 300 (e.g., the device 300 may not temporarily store or cache the data, or may store the data for only as long as it takes the node to process the data for streaming). Still further, the device 300 may stream data without using lossy data compression or any other techniques that may cause loss of original information.
In an embodiment, the device 300 temporarily stores at least some of the collected data in its cache 315, and pushes at least some of the data from its cache 315 when the cache 315 is filled to a particular threshold. The threshold of the cache may be adjustable. In some scenarios, the device 300 pushes at least some of data from its cache 315 when a resource (e.g., a bandwidth of the network 105, the processor 308, or some other resource) is sufficiently available. An availability threshold of a particular resource may be adjustable.
In an embodiment, the device 300 temporarily stores at least some of the collected data in its cache 315, and pushes at least some of the data stored in its cache 315 at periodic intervals. The periodicity of a particular time interval at which data is pushed may be based on a type of the data, the type of the device 300, the location of the device 300, and/or other criteria. The periodicity of a particular time interval may be adjustable. In some embodiments, the device 300 provides cached data in response to a request (e.g., from the process control big data appliance 102).
Turning to the flash memory 320 of the device 300, the flash memory 320 may be included in the memory 310, or may be a separate memory component (such as a solid-state drive) that is accessible to the multi-processing element processor 308. The flash memory 320 may be included in at least some of the memories MX shown in
In an embodiment, all data that is generated by, created by, received at, or observed by the device 300 is caused to be stored in the unitary, logical data storage area. For example, at least a portion of all observed data continually streamed to the unitary, logical data storage area. Observed data that is not immediately streamed may be continually and temporarily stored in the cache 315 (and, in some cases, the flash memory 320). Additionally, the contents of the cache 315 are continually transferred to the process control system big data appliance 102 to free the cache 315 to temporarily store subsequent observed data. Thus, a complete history of operations and device configurations in the process plant 10 is always available at the big data appliance 102 to support operator trends, process analysis, model building, data mining, and other relevant activities.
In transferring data to the big data appliance 102, the device 300 may cause at least a portion of the data in the cache 315 to be transmitted to the unitary, logical data storage area 120 or to an access application corresponding to the data storage area 120 of big data storage appliance 102 via one or more communications networks (e.g., the network backbone 105). Alternatively or additionally, the device 300 may cause at least a portion of the data in the cache 315 to be streamed (e.g., utilizing the SCTP) to the unitary, logical data storage area 120 or to the access application. In an embodiment, the process control system big data appliance 102 or the access application is a subscriber to a streaming service that delivers the cached data from the device 300. For example, the device 300 is a host of the streaming service.
In some embodiments, devices 300 that support big data in process control systems may be utilized for layered or leveled data caching and transmission in a process control network or system 10. In an example scenario, a device 300 transmits its cached data to one or more other intermediate devices or nodes, and the one or more other intermediate devices or nodes, in turn, cache the received data, and cause the received data to be forwarded from its cache for historization at the unitary, logical data storage area (e.g., the process control system big data storage area 120). In an embodiment, in addition to forwarding other devices' data, the one or more intermediate devices collects or captures its own respective directly generated, created or received data, and causes its respective collected data to be transmitted to the big data storage area 120 for historization. The one or more intermediate devices or nodes are located or disposed between the device 300 and the big data storage area 120 so that the location of the one or more intermediate devices or nodes is nearer, closer, or more proximate to the big data storage area 120 within the network 105 than is the location of the device 300.
Each of the process control devices 350a-350c, 351a, 352a and 352b may be an embodiment of the device 300 illustrated in
Furthermore,
To illustrate, at the level 350, each of the field devices 350a-350c causes the contents of the cached data in its respective memory storage M7-M9 to be delivered to the I/O device 351a, such as via the process control system big data network 105 or via another communications network. As shown in
At the level 351, the I/O device 351a caches, in the memory storage M10, the data received from the field devices 350a-350c (and, in some embodiments, also caches data received from other devices) along with other data that the I/O device 351a directly generates and receives. The data that is collected and cached at the I/O device 351a (including the contents of the cache of the field devices 350a-350c) may then be transmitted and/or streamed to the controllers 352a and 352b, such as by using the communications network 105 or some other communications network. In an embodiment, a portion of the cached data at the I/O device 351a is transmitted to the controller 352a, and a different portion of the cached data at the I/O device 351a is transmitted to the controller 352b. The controllers 352a, 352b are shown in
At the level 352, the controllers 352a and 352b each cache, in respective memory storages M11 and M12, respective data received from the I/O device 351a, and each aggregate the data from the device 351a with data that the controllers 352a and 352b themselves each directly generate and receive. In
Each of the controllers 352a and 352b may transmit at least some of its respective cached data to one or more appliance data receivers 122a, 122b (e.g., by using the network backbone 105). In an embodiment, at least one of the controllers 352a or 352b pushes at least some of the data from its respective cache (e.g., the memory storage M11 or M12) when the cache is filled to a particular threshold. The threshold of the cache may be adjustable, in an embodiment. At least one of the controllers 352a or 352b may push at least some of data from the respective cache when a resource (e.g., a bandwidth of the network 105 or some other resource) is sufficiently available. An availability threshold of a particular resource may be adjustable, in an embodiment.
In some embodiments, at least one of the controllers 352a or 352b pushes at least some of the data stored in the respective cache at periodic intervals. The periodicity of a particular time interval at which data is pushed may be based on a type of the data, the type of controller, the location of the controller, and/or other criteria, and the periodicity of a particular time interval may be adjustable. In some embodiments, at least one of the controllers 352a or 352b provides data in response to a request (e.g., from the process control big data appliance 102).
In some embodiments, at least one of the controllers 352a or 352b streams at least some of its respective collected data in real-time as the data is generated by, created by, or received at each of the controllers 352a and 352b (e.g., the controller may not store or cache the data, or may store the data for only as long as it takes the controller to process the data for streaming). For example, at least some of the data is streamed to the appliance data receivers 122a, 122b by using a streaming protocol. In an embodiment, at least one of the controllers 352a, 352b hosts a respective streaming service, and at least one of the data receivers 122a, 122b and/or the data storage area 120 may subscribe to the streaming service.
Accordingly, transmitted data may be received by the appliance data receivers 122a and 122b, for example, via the network backbone 105. In an embodiment, a particular appliance data receiver 122a or 122b is designated to receive data from one or more particular devices or nodes. In an embodiment, a particular appliance data receiver 122a or 122b is designated to receive data from only one or more particular types of devices or nodes (e.g., controllers, routers, or user interface devices). In some embodiments, a particular appliance data receiver 122a or 122b is designated to receive only one or more particular types of data (e.g., process control data only or network management data only).
The appliance data receivers 122a and 122b may cause the data to be stored or historized in the big data appliance storage area 120, e.g., as part of the big data set corresponding to the process plant 10. In an example, the data received by the appliance data receivers 122a and 122b is stored in the data storage area 120 using the process control big data schema. In
In an embodiment, data that is received via the plurality of appliance data receivers 122a and 122b is integrated so that data from multiple sources may be combined (e.g., into a same group of rows of the data storage area 120). Typically, but not necessarily, data that is received via the plurality of appliance data receivers 122a and 122b is stored in a raw format in the big data appliance storage area 120. In some scenarios, at least some of the received raw data may be cleaned to remove noise and inconsistent or outlier data. For example, an appliance request servicer 125a, 125b may request the retrieval of data stored in the big data appliance storage area 120 in a raw format or in a cleaned format. If cleaned data is requested, the process control system big data appliance 102 may retrieve raw data from the storage area 120 and clean the retrieved data prior to providing the cleaned data to the request servicer 125a, 125b
Turning now to
Additionally, each of the devices 380a-380c, 381a, 381b, 382a and 382b may be an embodiment of the device 300 illustrated in
As shown in
At the level 381, the devices 381a and 381b are shown as historian devices configured to temporarily store (e.g., cache) data received from the devices 380a-380c and/or other data that is accumulated throughout the process control system 10 in the respective memory storages M17 and M18. In some embodiments, the historian devices 381a and 381b are configured to receive specific types of data on a level or data from specific devices or nodes on the level. For example, the historian device 381a receives data from all devices or nodes on the level 380. In another example, the historian device 381a receives data from only field devices (e.g., the field device 380a) and networking devices (e.g., the router 380b) on the level 380. In still another example, the historian device 381b receives only user interface-related data such as user commands, user queries, etc. from user interface devices (e.g., the user interface device 380c) on the level 380.
As shown in
Generally, various types of data may be cached at different nodes of the process control system big data network 100 using different leveling or layering schemes. In an embodiment, data corresponding to controlling a process is cached and delivered in a layered manner using provider devices 110 whose primary functionality is control (e.g., field devices, I/O devices, controllers, such as in the example scenario illustrated by
In an embodiment, leveled or layered data caching and transmission is performed by nodes 110 that communicate with each other using the process control system big data network backbone 105. In an embodiment, at some nodes 110 involved in layered or leveled caching communicate cached data to nodes 110 at a different level using another communications network and/or other protocol, such as HART, WirelessHART, Fieldbus, DeviceNet, WiFi, Ethernet, or other protocol.
Of course, while leveled or layered caching has been discussed with respect to provider devices or nodes 110, the concepts and techniques may apply equally to user interface devices nodes 112 and/or to other types of devices or nodes 115 that support big data in process control plants and systems. In an embodiment, a subset of the devices or nodes 108 perform leveled or layered data caching and transmission, while another subset of the devices or nodes 108 cause their cached/collected data to be directly delivered to the process control big data appliance 102 without being cached or stored at an intermediate node. In some embodiments, historian nodes cache data from multiple different types of devices or nodes, e.g., from a provider device 110 and from a user interface device 112.
At a block 402, data may be collected at a device that supports big data in process control plants or networks. The device may be communicatively coupled to a communications network of a process plant or process control system, such as the process control system big data network 100. The device may be a field device, a process controller, an I/O device, a gateway device, an access point, a routing device, a network management device, a user interface device, a historian device, or some other device configured to collect big data associated with the process plant or with a process controlled by the process plant. The collected data may include measurement data, event data, batch data, calculated data, configuration data and continuous data. Accordingly, the collected data generally includes all types of data that are generated by, created by, received at, or observed by the device. The data may be collected without an identification of the data being included a priori in a configuration of the device. Further, the measurement and control data, as well as various other types of data, may be collected at the process control device at a rate of generation by the device, a rate of creation by the device, or at a rate of reception at the device, again without requiring the rate to be included a priori in the configuration of the device.
At a block 404, the collected data may be stored in a cache along with an indication of when the data was captured or collected (e.g., a timestamp) at the device. The cache is included in the device, for example. In an embodiment, the data and its respective timestamp may be stored in an entry of the cache. In embodiments where multiple values of the data are obtained over time (block 402), each value may be stored, along with its respective timestamp, in the same entry or in a different entry of the cache. The schema utilized by the cache to store entries may be included in a schema utilized by a data storage entity at which the cached data is to be historized, such as the process control big data storage area 120 or other suitable big data storage area. In some embodiments, the block 404 is omitted, such as when collected data is immediately streamed from the device to be historized at a process control system big data storage area.
At a block 406, at least a portion of the data stored in the cache is caused to be transmitted for storage to a unitary, logical storage area corresponding to the process plant (e.g. the big data storage area 120 in
In an embodiment, at least a portion of the data that is transmitted to the unitary, logical storage area for storage (block 406) is transmitted, via the communications network, to other process control devices or nodes disposed in the communications network between the process control device and the unitary logical data storage area. The other process control devices or nodes may be configured to temporarily store the at least the portion of the data and forward the at least a portion of the data to the unitary, logical data storage area. In an embodiment, at least a portion of the data that is transmitted to the unitary, logical storage area is also transmitted to other devices or nodes of the process control system or plant 10.
Embodiments of the techniques described in the present disclosure may include any number of the following aspects, either alone or combination:
1. A method of delivering data using a device communicatively coupled to a communications network of a process plant, where the process plant includes devices and equipment configured to control one or more processes. The method may comprise collecting data at the device, where the data includes at least one of: (i) data that is generated by the device (e.g., for transmission from the device), (ii) data that is created by the device, or (iii) data that is received at the device. The data may correspond to at least one of the process plant or to a process controlled by the process plant, and a type of the device may be included in a set of device types, where the set of device types includes a field device and a controller. The method may further include storing the collected data in a cache of the device, and causing at least a portion of the collected data to be transmitted for storage in a unitary, logical data storage area of a process control big data appliance corresponding to the process plant. The unitary, logical data storage area may be configured to store, using a common format, multiple types of data from a set of types of data corresponding to at least one of the process plant or the process controlled by the process plant, and the set of types of data may include continuous data, event data, measurement data, batch data, calculated data, and configuration data.
2. The method of the preceding aspect, wherein collecting the data comprises at least one of: collecting all data that is generated for transmission by the device, collecting all data created by the device, or collecting all data that is received at the device.
3. The method of any of the preceding aspects, wherein collecting the data comprises at least one of: collecting data that is generated for transmission by the device at a rate of generation, collecting data that is created by the device at a rate of creation, or collecting all data that is received at the device at a rate of reception.
4. The method of any of the preceding aspects, wherein collecting the data at the device comprises collecting, at the device, at least one type of data included in the set of types of data.
5. The method of any of the preceding aspects, wherein: the data is first data, the device is a first device, and the set of device types further includes an input/output (I/O) device having a field device interface and a controller interface. Additionally, the method may further comprise receiving, at the first device, second data that is at least one of (i) generated for transmission by a second device, (ii) created by the second device, or (iii) received at the second device, where the second device has a device type of one of the field device, the controller, or the I/O device. The method may include storing the second data in the cache of the first device, and causing at least a portion of the second collected data to be transmitted for storage in the unitary, logical data storage area of the process control big data appliance.
6. The method of any of the preceding aspects, wherein the first device has a device type of one of the field device, the controller, or the I/O device.
7. The method of any of the preceding aspects, wherein causing the at least the portion of the second collected data to be transmitted comprises integrally transmitting the at least the portion of the second collected data with the at least the portion of the first collected data.
8. The method of any of the preceding aspects, wherein storing the collected data in the cache includes storing, in conjunction with the collected data in the cache, indications of respective times of generation or reception of the collected data; and wherein causing the at least the portion of the collected data to be transmitted comprises causing the at least the portion of the collected data and the respective times of generation or reception of the at least the portion of the collected data to be transmitted.
9. The method of any of the preceding aspects, wherein storing the collected data in the cache of the device comprises storing the collected data in the cache using a schema that is included in a schema corresponding to the common format used by the unitary, logical data storage area.
10. The method of any of the preceding aspects, wherein causing the data to be transmitted comprises streaming the data.
11. The method of any of the preceding aspects, wherein streaming the data comprises streaming the data using a stream control transmission protocol (SCTP).
12. The method of any of the preceding aspects, further comprising providing a streaming service via which the data is streamed to one or more subscribers of the streaming service.
13. The method of any of the preceding aspects, wherein causing the at least the portion of the data to be transmitted for storage in the unitary, logical data storage area comprises transmitting, via a communications network, the at least the portion of the data to another device disposed in the communications network between the device and the unitary logical data storage area.
14. The method of any of the preceding aspects, wherein transmitting the at least the portion of the data to the another device comprises transmitting the at least the portion of the data to one of: a process control device configured to control the process in real-time in the process plant, a network management or routing device, or another device configured to temporarily store the at least the portion of the data and to forward the at least a portion of the data to the unitary, logical data storage area.
15. The method of any of the preceding aspects, wherein the set of devices types further includes an input/output (I/O) device having a field device interface and a controller interface, a user interface device, a gateway device, an access point, a routing device, and a network management device.
16. A device for controlling a process in a process plant includes an interface to a communications network of the process plant and a cache configured to store data (e.g., temporarily store data). The data may include at least one of: (i) data generated for transmission by the device, (ii) data created by the device, or (iii) data received by the device, and the data may correspond to at least one of the process plant or the process controlled in the process plant. The device may include a multi-processing element processor having at least one processing element designated to cause the data to be stored in the cache and to cause at least a portion of the data to be transmitted, via the communications network, for storage at a centralized data storage area corresponding to the process plant. The device may be a process control device, for example, a field device configured to perform a physical function to control the process, a controller configured to receive an input and generate, based on the input, an output to control the process, or an input/output (I/O) device disposed between and communicatively connecting the field device and the controller. In an embodiment, the device may be configured to perform any portions of any of the preceding aspects.
17. The device of the preceding aspect, wherein at least one of: a first processing element of the multi-processing element processor is designated to cause the data to be stored in the cache; a second processing element of the multi-processing element processor is designated to cause the at least the portion of the data to be transmitted, or a third processing element of the multi-processing element processor is designated to operate the device to control the process in the process plant in real-time.
18. The device of any of the preceding aspects, wherein at least one of: the first processing element of the multi-processing element processor is exclusively designated to at least one of cause the data to be stored in the cache or cause the at least the portion of the data to be transmitted, or the third processing element of the multi-processing element processor is exclusively designated to operate the device to control the process in the process plant.
19. The device of any of the preceding aspects, wherein the centralized data storage area is a unitary, logical data storage area of a process control big data appliance corresponding to the process plant. The unitary, logical data storage area may be configured to store, using a common format, multiple types of data corresponding to at least one of the process plant or the process controlled in the process plant. The multiple types of data may be included in a set of types of data comprising continuous data, measurement data, event data, calculated data, configuration data, and batch data.
20. The device of any of the preceding aspects, wherein the common format of the unitary, logical data storage area comprises a common schema, the common schema including a local schema used to store the data in the cache of the device.
21. The device of any of the preceding aspects, wherein the multi-processing element processor is configured to cause the at least the portion of the data stored in the cache to be streamed via the communications network.
22. The device of any of the preceding aspects, wherein the multi-processing element processor is configured to provide a streaming service to which at least one of the centralized data storage area or an access application corresponding to the centralized data storage area subscribes.
23. The device of any of the preceding aspects, wherein the data stored in the cache includes at least one of measurement data, calculated data, configuration data, batch data, event data, or continuous data.
24. The device of any of the preceding aspects, wherein the data is stored in the cache in conjunction with respective timestamps. Each respective timestamp may be indicative of a time of data generation or reception of a respective datum included in the data, and the multi-processing element processor may be configured to cause the at least the portion of the data and the respective timestamps corresponding to the at least the portion of the data to be transmitted for storage at the centralized data storage area.
25. The device of any of the preceding aspects, wherein a configuration of the device excludes indications of one or more identities of data to be collected and stored in the cache.
26. The device of any of the preceding aspects, wherein the data to be stored in the cache includes at least one of (i) all data generated for transmission by the device, (ii) all data created by the device, or (iii) all data received by the device.
27. The device of any of the preceding aspects, further comprising a flash memory configured to store at least one of: (i) at least a portion of a configuration of the device, or (ii) a batch recipe corresponding to the device, wherein a content of the flash memory is accessed by the device to resume operations after exiting an off-line state.
28. The device of any of the preceding aspects, wherein the communications network includes at least one of a wired communications network or a wireless communications network.
29. The device of any of the preceding aspects, wherein the interface is a first interface, the communications network is a first communications network, and the device further comprises a second interface coupled to a second communications network different from the communications network, the second interface used by the device to at least one of transmit or receive signals to control the process in real-time.
30. A system for supporting big data in a process plant, wherein the system includes a communications network having a plurality of nodes. The communications network may be configured to deliver data to be stored at a unitary, logical data storage area, and the unitary, logical data storage area may be configured to store, using a common format, multiple types of data from a set of data types corresponding to at least one of the process plant or a process controlled by the process plant. The set of data types may include continuous data, event data, measurement data, batch data, calculated data, and configuration data.
Each node of the plurality of nodes may be configured to (i) cache respective first data that is at least one of generated by, created by, or received at the each node, and to (ii) cause at least a portion of the cached data to be transmitted, via the communications network, for storage or historization at the unitary, logical data storage area. At least one node of the plurality of nodes is further configured to (iii) receive second data that is at least one of generated by, created by, or received at another node of the plurality of nodes, and to (iv) cause the second data to be transmitted for storage at the unitary, logical data storage area. The system may include a device according to any of the preceding aspects, and/or may perform at least a portion of a method according to any of the preceding aspects.
31. The system of the preceding aspect, wherein the plurality of nodes includes a controller configured to receive a set of inputs, determine a value of an output, and cause the output to be transmitted to a field device to control the process in the process plant, and wherein the field device is configured to perform a physical function based on the output of the controller to control the process.
32. The system of any of the preceding aspects, wherein the communications network is a first communications network, and wherein the controller is configured to at least one of: receive at least one input of the set of inputs at an interface to a second communications network, or cause the output to be transmitted to the field device via the interface to the second communications network.
33. The system of any of the preceding aspects, wherein the field device is a first field device, the controller is included in the at least one node of the plurality of nodes configured to receive the second data, and the another node is the first field device or a second field device.
34. The system of any of the preceding aspects, wherein: a first node of the plurality of nodes is disposed in the communications network between a second node of the plurality of nodes and the unitary, logical data storage area, the first node is included in the at least one node of the plurality of nodes configured to receive the second data that is at least one of generated by, created by, or received at the another node, and the another node is the second node.
35. The system of any of the preceding aspects, wherein the first node is further configured to cache the received second data.
36. The system of any of the preceding aspects, wherein the second node of the plurality of nodes is disposed in the communications network between the first node and a third node of the plurality of nodes, and wherein the second node is configured to (i) cache the second data, (ii) cache third data that is at least one of generated by, created by, or received at the third node, and (iii) cause the cached data to be transmitted to the first node to be forwarded for storage at the unitary, logical data storage area.
37. The system of any of the preceding aspects, wherein the communications network supports a streaming protocol.
38. The system of any of the preceding aspects, wherein at least one node of the plurality of nodes is configured to host a respective streaming service to which at least the unitary, logical data storage area or an access application of the unitary, logical data storage area subscribes.
39. The system of any of the preceding aspects, wherein a schema used by at least a subset of the plurality of nodes to cache the respective first data is included in a schema included in the common format used by the unitary, logical data storage area.
40. The system of any of the preceding aspects, wherein the plurality of nodes includes at least two devices from a set of devices including a controller, a field device, an input/output (I/O) device, a user interface device; a gateway device; an access point; a routing device; a historian device; and a network management device. The controller may be configured to receive a set of inputs, determine a value of an output, and cause the output to be transmitted to a field device to control the process in the process plant. The field device may be configured to perform a physical function based on the output of the controller to control the process, and the I/O device may include a field device interface and a controller interface.
41. Any number of any of the above aspects in combination with any number of any other of the above claims or aspects.
When implemented in software, any of the applications, services, and engines described herein may be stored in any tangible, non-transitory computer readable memory such as on a magnetic disk, a laser disk, solid state memory device, molecular memory storage device, or other storage medium, in a RAM or ROM of a computer or processor, etc. Although the example systems disclosed herein are disclosed as including, among other components, software and/or firmware executed on hardware, it should be noted that such systems are merely illustrative and should not be considered as limiting. For example, it is contemplated that any or all of these hardware, software, and firmware components could be embodied exclusively in hardware, exclusively in software, or in any combination of hardware and software. Accordingly, while the example systems described herein are described as being implemented in software executed on a processor of one or more computer devices, persons of ordinary skill in the art will readily appreciate that the examples provided are not the only way to implement such systems.
Thus, while the present invention has been described with reference to specific examples, which are intended to be illustrative only and not to be limiting of the invention, it will be apparent to those of ordinary skill in the art that changes, additions or deletions may be made to the disclosed embodiments without departing from the spirit and scope of the invention.
This application claims priority to U.S. Application No. 61/783,112, entitled “Collecting and Delivering Data to a Big Data Machine in a Process Control System” and filed on Mar. 14, 2013, the entire disclosure of which is hereby incorporated by reference herein. Additionally, this application is related to U.S. application Ser. No. 13/784,041, entitled “Big Data in Process Control Systems” and filed on Mar. 7, 2013, the entire disclosure of which is hereby incorporated by reference herein.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4451047 | Herd et al. | May 1984 | A |
| 4593367 | Slack et al. | Jun 1986 | A |
| 4901221 | Kodosky et al. | Feb 1990 | A |
| 4914568 | Kodosky et al. | Apr 1990 | A |
| 5111531 | Grayson et al. | May 1992 | A |
| 5164897 | Clark et al. | Nov 1992 | A |
| 5291587 | Kodosky et al. | Mar 1994 | A |
| 5301301 | Kodosky et al. | Apr 1994 | A |
| 5301336 | Kodosky et al. | Apr 1994 | A |
| 5475851 | Kodosky et al. | Dec 1995 | A |
| 5481740 | Kodosky | Jan 1996 | A |
| 5481741 | McKaskle et al. | Jan 1996 | A |
| 5497500 | Rogers et al. | Mar 1996 | A |
| 5544320 | Konrad | Aug 1996 | A |
| 5568491 | Beal et al. | Oct 1996 | A |
| 5598572 | Tanikoshi et al. | Jan 1997 | A |
| 5610828 | Kodosky et al. | Mar 1997 | A |
| 5652909 | Kodosky | Jul 1997 | A |
| D384050 | Kodosky | Sep 1997 | S |
| D384051 | Kodosky | Sep 1997 | S |
| D384052 | Kodosky | Sep 1997 | S |
| D387750 | Kodosky | Dec 1997 | S |
| 5732277 | Kodosky et al. | Mar 1998 | A |
| 5734863 | Kodosky et al. | Mar 1998 | A |
| 5737622 | Rogers et al. | Apr 1998 | A |
| 5801942 | Nixon et al. | Sep 1998 | A |
| 5801946 | Nissen et al. | Sep 1998 | A |
| 5821934 | Kodosky et al. | Oct 1998 | A |
| 5828851 | Nixon et al. | Oct 1998 | A |
| 5838563 | Dove et al. | Nov 1998 | A |
| 5856931 | McCasland | Jan 1999 | A |
| 5862052 | Nixon et al. | Jan 1999 | A |
| 5862054 | Li | Jan 1999 | A |
| 5909368 | Nixon et al. | Jun 1999 | A |
| 5917489 | Thurlow et al. | Jun 1999 | A |
| 5940294 | Dove | Aug 1999 | A |
| 5971747 | Lemelson et al. | Oct 1999 | A |
| 5980078 | Krivoshein et al. | Nov 1999 | A |
| 5987246 | Thomsen et al. | Nov 1999 | A |
| 5988847 | McLaughlin et al. | Nov 1999 | A |
| 5990906 | Hudson et al. | Nov 1999 | A |
| 5995916 | Nixon et al. | Nov 1999 | A |
| 6009422 | Ciccarelli | Dec 1999 | A |
| 6032208 | Nixon et al. | Feb 2000 | A |
| 6064409 | Thomsen et al. | May 2000 | A |
| 6078320 | Dove et al. | Jun 2000 | A |
| 6098116 | Nixon et al. | Aug 2000 | A |
| 6167464 | Kretschmann | Dec 2000 | A |
| 6173438 | Kodosky et al. | Jan 2001 | B1 |
| 6178504 | Fieres et al. | Jan 2001 | B1 |
| 6195591 | Nixon et al. | Feb 2001 | B1 |
| 6219628 | Kodosky et al. | Apr 2001 | B1 |
| 6266726 | Nixon et al. | Jul 2001 | B1 |
| 6278374 | Ganeshan | Aug 2001 | B1 |
| 6285966 | Brown et al. | Sep 2001 | B1 |
| 6295513 | Thackston | Sep 2001 | B1 |
| 6324877 | Neeley | Dec 2001 | B2 |
| 6347253 | Fujita et al. | Feb 2002 | B1 |
| 6421570 | McLaughlin et al. | Jul 2002 | B1 |
| 6442515 | Varma et al. | Aug 2002 | B1 |
| 6463352 | Tadokoro et al. | Oct 2002 | B1 |
| 6529780 | Soergel et al. | Mar 2003 | B1 |
| 6535883 | Lee et al. | Mar 2003 | B1 |
| 6563430 | Kemink et al. | May 2003 | B1 |
| 6584601 | Kodosky et al. | Jun 2003 | B1 |
| 6608638 | Kodosky et al. | Aug 2003 | B1 |
| 6609036 | Bickford | Aug 2003 | B1 |
| 6658114 | Farn et al. | Dec 2003 | B1 |
| 6701285 | Salonen | Mar 2004 | B2 |
| 6715078 | Chasko et al. | Mar 2004 | B1 |
| 6715139 | Kodosky et al. | Mar 2004 | B1 |
| 6763515 | Vazquez et al. | Jul 2004 | B1 |
| 6768116 | Berman et al. | Jul 2004 | B1 |
| 6772017 | Dove et al. | Aug 2004 | B1 |
| 6784903 | Kodosky et al. | Aug 2004 | B2 |
| 6847850 | Grumelart | Jan 2005 | B2 |
| 6868538 | Nixon et al. | Mar 2005 | B1 |
| 6917839 | Bickford | Jul 2005 | B2 |
| 6934667 | Kodosky et al. | Aug 2005 | B2 |
| 6934668 | Kodosky et al. | Aug 2005 | B2 |
| 6954724 | Kodosky et al. | Oct 2005 | B2 |
| 6961686 | Kodosky et al. | Nov 2005 | B2 |
| 6965886 | Govrin et al. | Nov 2005 | B2 |
| 6970758 | Shi et al. | Nov 2005 | B1 |
| 6971066 | Schultz et al. | Nov 2005 | B2 |
| 6983228 | Kodosky et al. | Jan 2006 | B2 |
| 6993466 | Kodosky et al. | Jan 2006 | B2 |
| 7000190 | Kudukoli et al. | Feb 2006 | B2 |
| 7006881 | Hoffberg et al. | Feb 2006 | B1 |
| 7010470 | Kodosky et al. | Mar 2006 | B2 |
| 7062718 | Kodosky et al. | Jun 2006 | B2 |
| 7072722 | Colonna et al. | Jul 2006 | B1 |
| 7123974 | Hamilton | Oct 2006 | B1 |
| 7134086 | Kodosky | Nov 2006 | B2 |
| 7134090 | Kodosky et al. | Nov 2006 | B2 |
| 7143149 | Oberg et al. | Nov 2006 | B2 |
| 7143289 | Denning et al. | Nov 2006 | B2 |
| 7177786 | Kodosky et al. | Feb 2007 | B2 |
| 7185287 | Ghercioiu et al. | Feb 2007 | B2 |
| 7200838 | Kodosky et al. | Apr 2007 | B2 |
| 7210117 | Kudukoli et al. | Apr 2007 | B2 |
| 7213057 | Trethewey et al. | May 2007 | B2 |
| 7216334 | Kodosky et al. | May 2007 | B2 |
| 7219306 | Kodosky et al. | May 2007 | B2 |
| 7222131 | Grewal et al. | May 2007 | B1 |
| 7283914 | Poorman et al. | Oct 2007 | B2 |
| 7283971 | Levine et al. | Oct 2007 | B1 |
| 7302675 | Rogers et al. | Nov 2007 | B2 |
| 7314169 | Jasper et al. | Jan 2008 | B1 |
| 7340737 | Ghercioiu et al. | Mar 2008 | B2 |
| 7343605 | Langkafel et al. | Mar 2008 | B2 |
| 7346404 | Eryurek et al. | Mar 2008 | B2 |
| 7367028 | Kodosky et al. | Apr 2008 | B2 |
| 7478337 | Kodosky et al. | Jan 2009 | B2 |
| 7506304 | Morrow et al. | Mar 2009 | B2 |
| 7530052 | Morrow et al. | May 2009 | B2 |
| 7530113 | Braun | May 2009 | B2 |
| 7536548 | Batke et al. | May 2009 | B1 |
| RE40817 | Krivoshein et al. | Jun 2009 | E |
| 7541920 | Tambascio et al. | Jun 2009 | B2 |
| 7548873 | Veeningen et al. | Jun 2009 | B2 |
| 7558711 | Kodosky et al. | Jul 2009 | B2 |
| 7565306 | Apostolides | Jul 2009 | B2 |
| 7574690 | Shah et al. | Aug 2009 | B2 |
| 7594220 | Kodosky et al. | Sep 2009 | B2 |
| 7598856 | Nick et al. | Oct 2009 | B1 |
| 7606681 | Esmaili et al. | Oct 2009 | B2 |
| 7616095 | Jones et al. | Nov 2009 | B2 |
| 7617542 | Vataja | Nov 2009 | B2 |
| 7627860 | Kodosky et al. | Dec 2009 | B2 |
| 7630914 | Veeningen et al. | Dec 2009 | B2 |
| 7640007 | Chen et al. | Dec 2009 | B2 |
| 7644052 | Chang et al. | Jan 2010 | B1 |
| 7650264 | Kodosky et al. | Jan 2010 | B2 |
| 7653563 | Veeningen et al. | Jan 2010 | B2 |
| 7668608 | Nixon et al. | Feb 2010 | B2 |
| 7676281 | Hood et al. | Mar 2010 | B2 |
| 7680546 | Gilbert et al. | Mar 2010 | B2 |
| 7684877 | Weatherhead et al. | Mar 2010 | B2 |
| RE41228 | Kodosky et al. | Apr 2010 | E |
| 7694273 | Kodosky et al. | Apr 2010 | B2 |
| 7707014 | Kodosky et al. | Apr 2010 | B2 |
| 7715929 | Skourup et al. | May 2010 | B2 |
| 7716489 | Brandt et al. | May 2010 | B1 |
| 7720727 | Keyes et al. | May 2010 | B2 |
| 7818715 | Kodosky et al. | Oct 2010 | B2 |
| 7818716 | Kodosky et al. | Oct 2010 | B2 |
| 7827122 | Campbell, Jr. et al. | Nov 2010 | B1 |
| 7831914 | Kodosky et al. | Nov 2010 | B2 |
| 7844908 | Kodosky et al. | Nov 2010 | B2 |
| 7853431 | Samardzija et al. | Dec 2010 | B2 |
| 7865349 | Kodosky et al. | Jan 2011 | B2 |
| 7882490 | Kodosky et al. | Feb 2011 | B2 |
| 7882491 | Kodosky et al. | Feb 2011 | B2 |
| 7925979 | Forney et al. | Apr 2011 | B2 |
| 7930639 | Baier et al. | Apr 2011 | B2 |
| 7934095 | Laberteaux et al. | Apr 2011 | B2 |
| 7937665 | Vazquez et al. | May 2011 | B1 |
| 7962440 | Beier et al. | Jun 2011 | B2 |
| 7978059 | Petite et al. | Jul 2011 | B2 |
| 7979843 | Kodosky et al. | Jul 2011 | B2 |
| 7984423 | Kodosky et al. | Jul 2011 | B2 |
| 7987448 | Kodosky et al. | Jul 2011 | B2 |
| 8014722 | Abel et al. | Sep 2011 | B2 |
| 8028241 | Kodosky et al. | Sep 2011 | B2 |
| 8028242 | Kodosky et al. | Sep 2011 | B2 |
| 8055787 | Victor et al. | Nov 2011 | B2 |
| 8060834 | Lucas et al. | Nov 2011 | B2 |
| 8073967 | Peterson et al. | Dec 2011 | B2 |
| 8074201 | Ghercioiu et al. | Dec 2011 | B2 |
| 8099712 | Kodosky et al. | Jan 2012 | B2 |
| 8102400 | Cook et al. | Jan 2012 | B1 |
| 8126964 | Pretlove et al. | Feb 2012 | B2 |
| 8132225 | Chand et al. | Mar 2012 | B2 |
| 8146053 | Morrow et al. | Mar 2012 | B2 |
| 8166296 | Buer et al. | Apr 2012 | B2 |
| 8171137 | Parks et al. | May 2012 | B1 |
| 8185217 | Thiele | May 2012 | B2 |
| 8185495 | Clark et al. | May 2012 | B2 |
| 8185832 | Kodosky et al. | May 2012 | B2 |
| 8185833 | Kodosky et al. | May 2012 | B2 |
| 8185871 | Nixon et al. | May 2012 | B2 |
| 8190888 | Batke et al. | May 2012 | B2 |
| 8191005 | Baier et al. | May 2012 | B2 |
| 8214455 | Baier et al. | Jul 2012 | B2 |
| 8218651 | Eshet et al. | Jul 2012 | B1 |
| 8219669 | Agrusa et al. | Jul 2012 | B2 |
| 8224496 | Musti et al. | Jul 2012 | B2 |
| 8239848 | Ghercioiu et al. | Aug 2012 | B2 |
| 8266066 | Wezter et al. | Sep 2012 | B1 |
| 8290762 | Kodosky et al. | Oct 2012 | B2 |
| 8307330 | Kumar et al. | Nov 2012 | B2 |
| 8316313 | Campney et al. | Nov 2012 | B2 |
| 8321663 | Medvinsky et al. | Nov 2012 | B2 |
| 8327130 | Wilkinson, Jr. et al. | Dec 2012 | B2 |
| 8350666 | Kore | Jan 2013 | B2 |
| 8359567 | Kornerup et al. | Jan 2013 | B2 |
| 8397172 | Kodosky et al. | Mar 2013 | B2 |
| 8397205 | Kornerup et al. | Mar 2013 | B2 |
| 8413118 | Kodosky et al. | Apr 2013 | B2 |
| 8417360 | Sustaeta et al. | Apr 2013 | B2 |
| 8417595 | Keyes et al. | Apr 2013 | B2 |
| 8418071 | Kodosky et al. | Apr 2013 | B2 |
| 8429627 | Jedlicka et al. | Apr 2013 | B2 |
| 8448135 | Kodosky | May 2013 | B2 |
| 8521332 | Tiemann et al. | Aug 2013 | B2 |
| 8532795 | Adavi et al. | Sep 2013 | B2 |
| 8570922 | Pratt, Jr. et al. | Oct 2013 | B2 |
| 8612870 | Kodosky et al. | Dec 2013 | B2 |
| 8624725 | MacGregor | Jan 2014 | B1 |
| 8640112 | Yi et al. | Jan 2014 | B2 |
| 8656351 | Kodosky et al. | Feb 2014 | B2 |
| 8688780 | Gordon et al. | Apr 2014 | B2 |
| 8781776 | Onda et al. | Jul 2014 | B2 |
| 8832236 | Hernandez et al. | Sep 2014 | B2 |
| 8943469 | Kumar et al. | Jan 2015 | B2 |
| 8977851 | Neitzel et al. | Mar 2015 | B2 |
| 9002973 | Panther | Apr 2015 | B2 |
| 9021021 | Backholm et al. | Apr 2015 | B2 |
| 9024972 | Bronder et al. | May 2015 | B1 |
| 9038043 | Fleetwood et al. | May 2015 | B1 |
| 9047007 | Kodosky et al. | Jun 2015 | B2 |
| 9088665 | Boyer et al. | Jul 2015 | B2 |
| 9098164 | Kodosky | Aug 2015 | B2 |
| 9110558 | Kodosky | Aug 2015 | B2 |
| 9119166 | Sheikh | Aug 2015 | B1 |
| 9122764 | Neitzel et al. | Sep 2015 | B2 |
| 9122786 | Cammert et al. | Sep 2015 | B2 |
| 9134895 | Dove et al. | Sep 2015 | B2 |
| 9229871 | Washiro | Jan 2016 | B2 |
| 9235395 | Kodosky et al. | Jan 2016 | B2 |
| 9338218 | Florissi et al. | May 2016 | B1 |
| 9361320 | Vijendra et al. | Jun 2016 | B1 |
| 9397836 | Nixon et al. | Jul 2016 | B2 |
| 9424398 | McLeod et al. | Aug 2016 | B1 |
| 9430114 | Dingman et al. | Aug 2016 | B1 |
| 9459809 | Chen et al. | Oct 2016 | B1 |
| 9532232 | Dewey et al. | Dec 2016 | B2 |
| 9541905 | Nixon et al. | Jan 2017 | B2 |
| 9558220 | Nixon et al. | Jan 2017 | B2 |
| 9652213 | MacCleery et al. | May 2017 | B2 |
| 9678484 | Nixon et al. | Jun 2017 | B2 |
| 9697170 | Nixon et al. | Jul 2017 | B2 |
| 9804588 | Blevins et al. | Oct 2017 | B2 |
| 9892353 | Lui et al. | Feb 2018 | B1 |
| 20020010694 | Navab et al. | Jan 2002 | A1 |
| 20020035495 | Spira et al. | Mar 2002 | A1 |
| 20020052715 | Maki | May 2002 | A1 |
| 20020054130 | Abbott et al. | May 2002 | A1 |
| 20020064138 | Saito et al. | May 2002 | A1 |
| 20020080174 | Kodosky et al. | Jun 2002 | A1 |
| 20020087419 | Andersson et al. | Jul 2002 | A1 |
| 20020094085 | Roberts | Jul 2002 | A1 |
| 20020120475 | Morimoto | Aug 2002 | A1 |
| 20020128998 | Kil et al. | Sep 2002 | A1 |
| 20020130846 | Nixon et al. | Sep 2002 | A1 |
| 20020138168 | Salonen | Sep 2002 | A1 |
| 20020138320 | Robertson et al. | Sep 2002 | A1 |
| 20020149497 | Jaggi | Oct 2002 | A1 |
| 20020159441 | Travaly et al. | Oct 2002 | A1 |
| 20020169514 | Eryurek et al. | Nov 2002 | A1 |
| 20030020726 | Charpentier | Jan 2003 | A1 |
| 20030023795 | Packwood et al. | Jan 2003 | A1 |
| 20030028495 | Pallante | Feb 2003 | A1 |
| 20030061295 | Oberg et al. | Mar 2003 | A1 |
| 20030083756 | Hsiung et al. | May 2003 | A1 |
| 20030084053 | Govrin et al. | May 2003 | A1 |
| 20030093309 | Tanikoshi et al. | May 2003 | A1 |
| 20030147351 | Greenlee | Aug 2003 | A1 |
| 20030154044 | Lundstedt et al. | Aug 2003 | A1 |
| 20030195934 | Peterson et al. | Oct 2003 | A1 |
| 20040005859 | Ghercioiu et al. | Jan 2004 | A1 |
| 20040012632 | King et al. | Jan 2004 | A1 |
| 20040014479 | Milman | Jan 2004 | A1 |
| 20040075689 | Schleiss et al. | Apr 2004 | A1 |
| 20040093102 | Liiri et al. | May 2004 | A1 |
| 20040117233 | Rapp | Jun 2004 | A1 |
| 20040133457 | Sadiq et al. | Jul 2004 | A1 |
| 20040153437 | Buchan | Aug 2004 | A1 |
| 20040153804 | Blevins et al. | Aug 2004 | A1 |
| 20040203874 | Brandt et al. | Oct 2004 | A1 |
| 20040204775 | Keyes et al. | Oct 2004 | A1 |
| 20040210330 | Birkle | Oct 2004 | A1 |
| 20040230328 | Armstrong | Nov 2004 | A1 |
| 20040233930 | Colby | Nov 2004 | A1 |
| 20050005259 | Avery et al. | Jan 2005 | A1 |
| 20050060111 | Ramillon et al. | Mar 2005 | A1 |
| 20050062677 | Nixon et al. | Mar 2005 | A1 |
| 20050080799 | Harnden et al. | Apr 2005 | A1 |
| 20050096872 | Blevins et al. | May 2005 | A1 |
| 20050130634 | Godfrey | Jun 2005 | A1 |
| 20050164684 | Chen et al. | Jul 2005 | A1 |
| 20050182650 | Maddox et al. | Aug 2005 | A1 |
| 20050187649 | Funk et al. | Aug 2005 | A1 |
| 20050213768 | Durham et al. | Sep 2005 | A1 |
| 20050222691 | Glas et al. | Oct 2005 | A1 |
| 20050222698 | Eryurek et al. | Oct 2005 | A1 |
| 20050264527 | Lin | Dec 2005 | A1 |
| 20060031826 | Hiramatsu | Feb 2006 | A1 |
| 20060064291 | Pattipatti et al. | Mar 2006 | A1 |
| 20060064472 | Mirho | Mar 2006 | A1 |
| 20060069717 | Mamou et al. | Mar 2006 | A1 |
| 20060087402 | Manning et al. | Apr 2006 | A1 |
| 20060168396 | LaMothe et al. | Jul 2006 | A1 |
| 20060200260 | Hoffberg et al. | Sep 2006 | A1 |
| 20060200771 | Nielsen et al. | Sep 2006 | A1 |
| 20060218107 | Young | Sep 2006 | A1 |
| 20060235741 | Deaton et al. | Oct 2006 | A1 |
| 20060241792 | Pretlove et al. | Oct 2006 | A1 |
| 20060288091 | Oh et al. | Dec 2006 | A1 |
| 20060291481 | Kumar | Dec 2006 | A1 |
| 20060294087 | Mordvinov | Dec 2006 | A1 |
| 20070005266 | Blevins et al. | Jan 2007 | A1 |
| 20070014406 | Scheidt et al. | Jan 2007 | A1 |
| 20070038889 | Wiggins et al. | Feb 2007 | A1 |
| 20070067725 | Cahill et al. | Mar 2007 | A1 |
| 20070078696 | Hardin | Apr 2007 | A1 |
| 20070112574 | Greene | May 2007 | A1 |
| 20070118516 | Li et al. | May 2007 | A1 |
| 20070130310 | Batke et al. | Jun 2007 | A1 |
| 20070130572 | Gilbert et al. | Jun 2007 | A1 |
| 20070132779 | Gilbert et al. | Jun 2007 | A1 |
| 20070139441 | Lucas et al. | Jun 2007 | A1 |
| 20070179645 | Nixon et al. | Aug 2007 | A1 |
| 20070185754 | Schmidt | Aug 2007 | A1 |
| 20070211079 | Nixon et al. | Sep 2007 | A1 |
| 20070239292 | Ehrman et al. | Oct 2007 | A1 |
| 20070250292 | Alagappan et al. | Oct 2007 | A1 |
| 20070265801 | Foslien et al. | Nov 2007 | A1 |
| 20070265866 | Fehling et al. | Nov 2007 | A1 |
| 20080040719 | Shimizu et al. | Feb 2008 | A1 |
| 20080046104 | Van Camp et al. | Feb 2008 | A1 |
| 20080058968 | Sharma et al. | Mar 2008 | A1 |
| 20080065243 | Fallman et al. | Mar 2008 | A1 |
| 20080065705 | Miller | Mar 2008 | A1 |
| 20080065706 | Miller et al. | Mar 2008 | A1 |
| 20080076431 | Fletcher et al. | Mar 2008 | A1 |
| 20080078189 | Ando | Apr 2008 | A1 |
| 20080079596 | Baier et al. | Apr 2008 | A1 |
| 20080082180 | Blevins et al. | Apr 2008 | A1 |
| 20080082181 | Miller et al. | Apr 2008 | A1 |
| 20080082195 | Samardzija | Apr 2008 | A1 |
| 20080097622 | Forney et al. | Apr 2008 | A1 |
| 20080103843 | Goeppert et al. | May 2008 | A1 |
| 20080104189 | Baker et al. | May 2008 | A1 |
| 20080125912 | Heilman et al. | May 2008 | A1 |
| 20080126352 | Case | May 2008 | A1 |
| 20080126665 | Burr | May 2008 | A1 |
| 20080143482 | Shoarinejad et al. | Jun 2008 | A1 |
| 20080174766 | Haaslahti et al. | Jul 2008 | A1 |
| 20080182592 | Cha et al. | Jul 2008 | A1 |
| 20080209443 | Suzuki | Aug 2008 | A1 |
| 20080249641 | Enver et al. | Oct 2008 | A1 |
| 20080274766 | Pratt et al. | Nov 2008 | A1 |
| 20080275971 | Pretlove et al. | Nov 2008 | A1 |
| 20080288321 | Dillon et al. | Nov 2008 | A1 |
| 20080297513 | Greenhill et al. | Dec 2008 | A1 |
| 20080301123 | Schneider et al. | Dec 2008 | A1 |
| 20090049073 | Cho | Feb 2009 | A1 |
| 20090065578 | Peterson et al. | Mar 2009 | A1 |
| 20090070337 | Romem et al. | Mar 2009 | A1 |
| 20090070589 | Nayak et al. | Mar 2009 | A1 |
| 20090089233 | Gach et al. | Apr 2009 | A1 |
| 20090089359 | Siorek et al. | Apr 2009 | A1 |
| 20090089709 | Baier et al. | Apr 2009 | A1 |
| 20090094531 | Danieli et al. | Apr 2009 | A1 |
| 20090097502 | Yamamoto | Apr 2009 | A1 |
| 20090112335 | Mehta et al. | Apr 2009 | A1 |
| 20090112532 | Foslien et al. | Apr 2009 | A1 |
| 20090210386 | Cahill | Aug 2009 | A1 |
| 20090210802 | Hawkins et al. | Aug 2009 | A1 |
| 20090210814 | Agrusa et al. | Aug 2009 | A1 |
| 20090216341 | Enkerud et al. | Aug 2009 | A1 |
| 20090249237 | Jundt et al. | Oct 2009 | A1 |
| 20090284383 | Wiles et al. | Nov 2009 | A1 |
| 20090294174 | Harmer et al. | Dec 2009 | A1 |
| 20090300535 | Skourup et al. | Dec 2009 | A1 |
| 20090319058 | Rovaglio et al. | Dec 2009 | A1 |
| 20090325603 | Van Os et al. | Dec 2009 | A1 |
| 20090327014 | Labedz et al. | Dec 2009 | A1 |
| 20100036779 | Sadeh-Koniecpol et al. | Feb 2010 | A1 |
| 20100069008 | Oshima et al. | Mar 2010 | A1 |
| 20100076642 | Hoffberg et al. | Mar 2010 | A1 |
| 20100082132 | Marruchella et al. | Apr 2010 | A1 |
| 20100082158 | Lakomiak et al. | Apr 2010 | A1 |
| 20100106282 | Mackelprang et al. | Apr 2010 | A1 |
| 20100127821 | Jones et al. | May 2010 | A1 |
| 20100127824 | Moschl et al. | May 2010 | A1 |
| 20100145476 | Junk et al. | Jun 2010 | A1 |
| 20100169785 | Jesudason | Jul 2010 | A1 |
| 20100185857 | Neitzel et al. | Jul 2010 | A1 |
| 20100190442 | Citrano, III et al. | Jul 2010 | A1 |
| 20100192122 | Esfahan et al. | Jul 2010 | A1 |
| 20100222899 | Blevins et al. | Sep 2010 | A1 |
| 20100262929 | Avery | Oct 2010 | A1 |
| 20100275135 | Dunton et al. | Oct 2010 | A1 |
| 20100286798 | Keyes et al. | Nov 2010 | A1 |
| 20100290351 | Toepke et al. | Nov 2010 | A1 |
| 20100290359 | Dewey et al. | Nov 2010 | A1 |
| 20100293019 | Keyes et al. | Nov 2010 | A1 |
| 20100293564 | Gould | Nov 2010 | A1 |
| 20100305736 | Arduini | Dec 2010 | A1 |
| 20100318934 | Blevins et al. | Dec 2010 | A1 |
| 20110022193 | Panaitescu | Jan 2011 | A1 |
| 20110046754 | Bromley et al. | Feb 2011 | A1 |
| 20110071869 | O'Brien et al. | Mar 2011 | A1 |
| 20110072338 | Caldwell | Mar 2011 | A1 |
| 20110098918 | Siliski et al. | Apr 2011 | A1 |
| 20110115816 | Brackney | May 2011 | A1 |
| 20110130848 | Tegnell et al. | Jun 2011 | A1 |
| 20110140864 | Bucci | Jun 2011 | A1 |
| 20110144777 | Firkins et al. | Jun 2011 | A1 |
| 20110191277 | Ag ndez Dominguez et al. | Aug 2011 | A1 |
| 20110238189 | Butera et al. | Sep 2011 | A1 |
| 20110258138 | Kulkarni et al. | Oct 2011 | A1 |
| 20110276896 | Zambetti et al. | Nov 2011 | A1 |
| 20110276908 | O'Riordan | Nov 2011 | A1 |
| 20110279323 | Hung et al. | Nov 2011 | A1 |
| 20110282793 | Mercuri et al. | Nov 2011 | A1 |
| 20110295722 | Reisman | Dec 2011 | A1 |
| 20120004743 | Anne et al. | Jan 2012 | A1 |
| 20120005270 | Harding et al. | Jan 2012 | A1 |
| 20120010758 | Francino et al. | Jan 2012 | A1 |
| 20120011180 | Kavaklioglu | Jan 2012 | A1 |
| 20120011511 | Horvitz et al. | Jan 2012 | A1 |
| 20120029661 | Jones et al. | Feb 2012 | A1 |
| 20120038458 | Toepke et al. | Feb 2012 | A1 |
| 20120040698 | Ferguson et al. | Feb 2012 | A1 |
| 20120078869 | Bellville | Mar 2012 | A1 |
| 20120095574 | Greenlee | Apr 2012 | A1 |
| 20120147862 | Poojary et al. | Jun 2012 | A1 |
| 20120163521 | Kirrmann et al. | Jun 2012 | A1 |
| 20120176491 | Garin et al. | Jul 2012 | A1 |
| 20120203728 | Levine | Aug 2012 | A1 |
| 20120226985 | Chervets et al. | Sep 2012 | A1 |
| 20120230309 | Junk | Sep 2012 | A1 |
| 20120239164 | Smith et al. | Sep 2012 | A1 |
| 20120249588 | Tison et al. | Oct 2012 | A1 |
| 20120271962 | Ivanov et al. | Oct 2012 | A1 |
| 20120290795 | Dowlatkhah | Nov 2012 | A1 |
| 20120331541 | Hamilton, II et al. | Dec 2012 | A1 |
| 20130006696 | Louie et al. | Jan 2013 | A1 |
| 20130007223 | Luby et al. | Jan 2013 | A1 |
| 20130013523 | Herrera Campos | Jan 2013 | A1 |
| 20130029686 | Moshfeghi | Jan 2013 | A1 |
| 20130041479 | Zhang et al. | Feb 2013 | A1 |
| 20130060354 | Choi et al. | Mar 2013 | A1 |
| 20130086591 | Haven | Apr 2013 | A1 |
| 20130095849 | Pakzad | Apr 2013 | A1 |
| 20130120449 | Ihara et al. | May 2013 | A1 |
| 20130127980 | Haddick et al. | May 2013 | A1 |
| 20130144404 | Godwin et al. | Jun 2013 | A1 |
| 20130144405 | Lo | Jun 2013 | A1 |
| 20130144605 | Brager et al. | Jun 2013 | A1 |
| 20130151563 | Addepalli et al. | Jun 2013 | A1 |
| 20130159200 | Paul et al. | Jun 2013 | A1 |
| 20130169526 | Gai et al. | Jul 2013 | A1 |
| 20130184847 | Fruh et al. | Jul 2013 | A1 |
| 20130197954 | Yankelevich et al. | Aug 2013 | A1 |
| 20130211555 | Lawson et al. | Aug 2013 | A1 |
| 20130212129 | Lawson et al. | Aug 2013 | A1 |
| 20130214902 | Pineau et al. | Aug 2013 | A1 |
| 20130217417 | Mohideen et al. | Aug 2013 | A1 |
| 20130231947 | Shusterman | Sep 2013 | A1 |
| 20130257627 | Rafael | Oct 2013 | A1 |
| 20130265857 | Foulds et al. | Oct 2013 | A1 |
| 20130282150 | Panther et al. | Oct 2013 | A1 |
| 20130318536 | Fletcher et al. | Nov 2013 | A1 |
| 20140006338 | Watson et al. | Jan 2014 | A1 |
| 20140015672 | Ponce | Jan 2014 | A1 |
| 20140039648 | Boult et al. | Feb 2014 | A1 |
| 20140067800 | Sharma | Mar 2014 | A1 |
| 20140079297 | Tadayon et al. | Mar 2014 | A1 |
| 20140089504 | Scholz et al. | Mar 2014 | A1 |
| 20140108985 | Scott et al. | Apr 2014 | A1 |
| 20140122806 | Lin et al. | May 2014 | A1 |
| 20140123276 | Bush et al. | May 2014 | A1 |
| 20140136652 | Narayanaswami et al. | May 2014 | A1 |
| 20140156032 | Jenkins et al. | Jun 2014 | A1 |
| 20140164603 | Castel et al. | Jun 2014 | A1 |
| 20140172961 | Clemmer et al. | Jun 2014 | A1 |
| 20140180671 | Osipova | Jun 2014 | A1 |
| 20140180970 | Hettenkofer et al. | Jun 2014 | A1 |
| 20140189520 | Crepps et al. | Jul 2014 | A1 |
| 20140201244 | Zhou | Jul 2014 | A1 |
| 20140232843 | Campbell | Aug 2014 | A1 |
| 20140250153 | Nixon et al. | Sep 2014 | A1 |
| 20140267599 | Drouin et al. | Sep 2014 | A1 |
| 20140273847 | Nixon et al. | Sep 2014 | A1 |
| 20140274123 | Nixon et al. | Sep 2014 | A1 |
| 20140277593 | Nixon et al. | Sep 2014 | A1 |
| 20140277594 | Nixon et al. | Sep 2014 | A1 |
| 20140277595 | Nixon et al. | Sep 2014 | A1 |
| 20140277596 | Nixon et al. | Sep 2014 | A1 |
| 20140277604 | Nixon et al. | Sep 2014 | A1 |
| 20140277605 | Nixon et al. | Sep 2014 | A1 |
| 20140277607 | Nixon et al. | Sep 2014 | A1 |
| 20140277615 | Nixon et al. | Sep 2014 | A1 |
| 20140277616 | Nixon et al. | Sep 2014 | A1 |
| 20140277617 | Nixon et al. | Sep 2014 | A1 |
| 20140277618 | Nixon et al. | Sep 2014 | A1 |
| 20140277656 | Nixon et al. | Sep 2014 | A1 |
| 20140278312 | Nixon et al. | Sep 2014 | A1 |
| 20140280497 | Nixon et al. | Sep 2014 | A1 |
| 20140280678 | Nixon et al. | Sep 2014 | A1 |
| 20140282015 | Nixon et al. | Sep 2014 | A1 |
| 20140282227 | Nixon et al. | Sep 2014 | A1 |
| 20140282257 | Nixon et al. | Sep 2014 | A1 |
| 20140297225 | Petroski et al. | Oct 2014 | A1 |
| 20140316579 | Taylor et al. | Oct 2014 | A1 |
| 20140358256 | Billi et al. | Dec 2014 | A1 |
| 20140359552 | Misra et al. | Dec 2014 | A1 |
| 20140372378 | Long et al. | Dec 2014 | A1 |
| 20140372561 | Hisano | Dec 2014 | A1 |
| 20140379296 | Nathan et al. | Dec 2014 | A1 |
| 20150024710 | Becker et al. | Jan 2015 | A1 |
| 20150067163 | Bahnsen et al. | Mar 2015 | A1 |
| 20150106578 | Warfield et al. | Apr 2015 | A1 |
| 20150172872 | Alsehly et al. | Jun 2015 | A1 |
| 20150177718 | Vartiainen et al. | Jun 2015 | A1 |
| 20150220080 | Nixon et al. | Aug 2015 | A1 |
| 20150222731 | Shinohara et al. | Aug 2015 | A1 |
| 20150246852 | Chen et al. | Sep 2015 | A1 |
| 20150261215 | Blevins et al. | Sep 2015 | A1 |
| 20150278397 | Hendrickson et al. | Oct 2015 | A1 |
| 20150296324 | Garaas et al. | Oct 2015 | A1 |
| 20150312721 | Singh et al. | Oct 2015 | A1 |
| 20150332188 | Yankelevich et al. | Nov 2015 | A1 |
| 20160098021 | Zornio et al. | Apr 2016 | A1 |
| 20160098037 | Zornio et al. | Apr 2016 | A1 |
| 20160098388 | Blevins et al. | Apr 2016 | A1 |
| 20160098647 | Nixon et al. | Apr 2016 | A1 |
| 20160132046 | Beoughter et al. | May 2016 | A1 |
| 20160261482 | Mixer et al. | Sep 2016 | A1 |
| 20160327942 | Nixon et al. | Nov 2016 | A1 |
| 20170102678 | Nixon et al. | Apr 2017 | A1 |
| 20170102693 | Kidd et al. | Apr 2017 | A1 |
| 20170102694 | Enver et al. | Apr 2017 | A1 |
| 20170102696 | Bell et al. | Apr 2017 | A1 |
| 20170103103 | Nixon et al. | Apr 2017 | A1 |
| 20170115648 | Nixon et al. | Apr 2017 | A1 |
| 20170154395 | Podgurny et al. | Jun 2017 | A1 |
| 20170199843 | Nixon et al. | Jul 2017 | A1 |
| 20170235298 | Nixon et al. | Aug 2017 | A1 |
| 20170236067 | Tjiong | Aug 2017 | A1 |
| 20180151037 | Morgenthau et al. | May 2018 | A1 |
| Number | Date | Country |
|---|---|---|
| 2010257310 | Jul 2012 | AU |
| 1409179 | Apr 2003 | CN |
| 1409232 | Apr 2003 | CN |
| 1537258 | Oct 2004 | CN |
| 1589423 | Mar 2005 | CN |
| 1757002 | Apr 2006 | CN |
| 1804744 | Jul 2006 | CN |
| 1805040 | Jul 2006 | CN |
| 1826565 | Aug 2006 | CN |
| 1864156 | Nov 2006 | CN |
| 1980194 | Jun 2007 | CN |
| 101097136 | Jan 2008 | CN |
| 101387882 | Mar 2009 | CN |
| 101449259 | Jun 2009 | CN |
| 201374004 | Dec 2009 | CN |
| 101713985 | May 2010 | CN |
| 101788820 | Jul 2010 | CN |
| 101802736 | Aug 2010 | CN |
| 101828195 | Sep 2010 | CN |
| 101867566 | Oct 2010 | CN |
| 102063097 | May 2011 | CN |
| 102124432 | Jul 2011 | CN |
| 102169182 | Aug 2011 | CN |
| 102175174 | Sep 2011 | CN |
| 102184489 | Sep 2011 | CN |
| 102200993 | Sep 2011 | CN |
| 102213959 | Oct 2011 | CN |
| 102239452 | Nov 2011 | CN |
| 102243315 | Nov 2011 | CN |
| 102278987 | Dec 2011 | CN |
| 202101268 | Jan 2012 | CN |
| 102349031 | Feb 2012 | CN |
| 102375453 | Mar 2012 | CN |
| 102378989 | Mar 2012 | CN |
| 102402215 | Apr 2012 | CN |
| 102436205 | May 2012 | CN |
| 102494630 | Jun 2012 | CN |
| 102494683 | Jun 2012 | CN |
| 102637027 | Aug 2012 | CN |
| 102640156 | Aug 2012 | CN |
| 102707689 | Oct 2012 | CN |
| 102710861 | Oct 2012 | CN |
| 102867237 | Jan 2013 | CN |
| 103106188 | May 2013 | CN |
| 103403686 | Nov 2013 | CN |
| 103576638 | Feb 2014 | CN |
| 104035392 | Sep 2014 | CN |
| 104049575 | Sep 2014 | CN |
| 19882113 | Jan 2000 | DE |
| 19882117 | Jan 2000 | DE |
| 0 308 390 | Mar 1989 | EP |
| 0 335 957 | Oct 1989 | EP |
| 1 344 291 | Sep 2003 | EP |
| 1 414 215-2 | Apr 2004 | EP |
| 1 564 647 | Aug 2005 | EP |
| 1 912 376 | Apr 2008 | EP |
| 2 003 813 | Dec 2008 | EP |
| 2 112 614 | Oct 2009 | EP |
| 2 180 441 | Apr 2010 | EP |
| 2 469 475 | Jun 2012 | EP |
| 1 344 291 | Aug 2012 | EP |
| 2 685 329 | Jan 2014 | EP |
| 2 704 401 | Mar 2014 | EP |
| 2 746 884 | Jun 2014 | EP |
| 2 801 939 | Nov 2014 | EP |
| 2 966 625 | Apr 2012 | FR |
| 2 336 977 | Nov 1999 | GB |
| 2 336 923 | Jun 2002 | GB |
| 2 403 028 | Dec 2004 | GB |
| 2 453 426 | Apr 2009 | GB |
| 2 512 984 | Oct 2014 | GB |
| 2 512 997 | Oct 2014 | GB |
| 2 532 849 | Jun 2016 | GB |
| 2 534 628 | Aug 2016 | GB |
| 2 537 457 | Oct 2016 | GB |
| 64-017105 | Jan 1989 | JP |
| 01-291303 | Nov 1989 | JP |
| 05-073131 | Mar 1993 | JP |
| 05-142033 | Jun 1993 | JP |
| 05-187973 | Jul 1993 | JP |
| 06-052145 | Feb 1994 | JP |
| 08-234951 | Sep 1996 | JP |
| 09-330861 | Dec 1997 | JP |
| 10-116113 | May 1998 | JP |
| 10-326111 | Dec 1998 | JP |
| 11-327628 | Nov 1999 | JP |
| 2000-214914 | Aug 2000 | JP |
| 2001-512593 | Aug 2001 | JP |
| 2001-265821 | Sep 2001 | JP |
| 2002-010489 | Jan 2002 | JP |
| 2002-024423 | Jan 2002 | JP |
| 2002-99325 | Apr 2002 | JP |
| 2003-295944 | Oct 2003 | JP |
| 2004-102765 | Apr 2004 | JP |
| 2004-171127 | Jun 2004 | JP |
| 2004-199624 | Jul 2004 | JP |
| 2004-227561 | Aug 2004 | JP |
| 2005-107758 | Apr 2005 | JP |
| 2005-216137 | Aug 2005 | JP |
| 2005-242830 | Sep 2005 | JP |
| 2005-332093 | Dec 2005 | JP |
| 2006-172462 | Jun 2006 | JP |
| 2006-221376 | Aug 2006 | JP |
| 2006-527426 | Nov 2006 | JP |
| 2007-137563 | Jun 2007 | JP |
| 2007-148938 | Jun 2007 | JP |
| 2007-207065 | Aug 2007 | JP |
| 2007-242000 | Sep 2007 | JP |
| 2007-286798 | Nov 2007 | JP |
| 2007-536631 | Dec 2007 | JP |
| 2007-536648 | Dec 2007 | JP |
| 2008-065821 | Mar 2008 | JP |
| 2008-158971 | Jul 2008 | JP |
| 2008-305419 | Dec 2008 | JP |
| 2009-064451 | Mar 2009 | JP |
| 2009-140380 | Jun 2009 | JP |
| 2009-211522 | Sep 2009 | JP |
| 2009-251777 | Oct 2009 | JP |
| 2010-527486 | Aug 2010 | JP |
| 2011-022920 | Feb 2011 | JP |
| 2011-034564 | Feb 2011 | JP |
| 2011-204237 | Oct 2011 | JP |
| 2011-204238 | Oct 2011 | JP |
| 2012-048762 | Mar 2012 | JP |
| 2012-069118 | Apr 2012 | JP |
| 2012-084162 | Apr 2012 | JP |
| 4-934482 | May 2012 | JP |
| 2012-215547 | Nov 2012 | JP |
| 2012-527059 | Nov 2012 | JP |
| 2014-116027 | Jun 2014 | JP |
| WO-0250971 | Jun 2002 | WO |
| WO-03073688 | Sep 2003 | WO |
| WO-2003073688 | Sep 2003 | WO |
| WO-2005083533 | Sep 2005 | WO |
| WO-2005109123 | Nov 2005 | WO |
| WO-2008042786 | Apr 2008 | WO |
| WO-2009021900 | Feb 2009 | WO |
| WO-2009046095 | Apr 2009 | WO |
| WO-2011120625 | Oct 2011 | WO |
| WO-2012016012 | Feb 2012 | WO |
| WO-2012022381 | Feb 2012 | WO |
| WO-2012096877 | Jul 2012 | WO |
| WO-2014005073 | Jan 2014 | WO |
| WO-2014145801 | Sep 2014 | WO |
| WO-2015138706 | Sep 2015 | WO |
| WO-2016057365 | Apr 2016 | WO |
| Entry |
|---|
| “Control Loop Foundation—Batch and Continuous Processes”, by Terrence Blevins and Mark Nixon, International Society of Automation, 2011, Chapter 7. |
| Search Report for Application No. GB1402311.3, dated Aug. 6, 2014. |
| Search Report for Application No. GB1403251.0, dated Aug. 8, 2014. |
| Woo, “Intel Drops a Big Data Shocker”, downloaded from the Internet at: <http://forbes.com/sites/bwoo/2013/02/27/intel-drops-a-big-data-shocker/?partner—ya> dated Feb. 27, 2013. |
| Search Report for Application No. GB1513617.9, dated Jan. 21, 2016. |
| International Search Report and Written Opinion for Application No. PCT/US2015,053931, dated Jan. 26, 2016. |
| Krumeich et al., “Big Data Analytics for Predictive Manufacturing Control—A Case Study from Process Industry,” IEEE International Congress on Big Data, pp. 530-537 (2014). |
| “IoT and Big Data Combine Forces,” (2013). Retrieved from the Internet at: URL:http://wiki.advantech.com/images/7/73/iot2013_whitepaper.pdf. |
| Bryner, “Smart Manufacturing: The Next Revolution,” Chemical Engineering Process (2012). Retrieved from the Internet at: URL:http://www.aiche.org/sites/default/files/ces/20121004a.pdf. |
| Building Smarter Manufacturing with the Internet of Things (IoT), (2014). Retrieved from the Internet at: URL:http://www.cisco.com/web/solutions/trends/iot/iot_in_manufacturing_january.pdf. |
| International Search Report and Written Opinion for Application No. PCT/US2015/020148, dated Jun. 18, 2015. |
| Smalley, “GE Invests in Project to Embed Predictive Analytics in Industrial Internet,” (2013). Retrieved from the Internet at: URL:http://data-informed.com/ge-invents-in-project-to-embed-predictive-analytics-in-industrial-internet/. |
| “ANSI/ISA-S5.4-1991 American National Standard Instrument Loop Diagrams” by Instrument Society of America, 1986, 22 pages. |
| Examination Report for Application No. GB1017192.4, dated May 28, 2014. |
| Examination Report for Application No. GB1017192.4, dated Sep. 5, 2013. |
| First Office Action for Chinese Application No. 201010589029.X, dated Dec. 10, 2013. |
| Notice of Reasons for Rejection for Japanese Application No. 2010-229513, dated Jul. 29, 2014. |
| Search Report for Application No. GB1017192.4, dated Feb. 15, 2011. |
| Search Report for Application No. GB1403407.8, dated Aug. 8, 2014. |
| Search Report for Application No. GB1403408.6, dated Aug. 8, 2014. |
| Search Report for Application No. GB1403471.4, dated Sep. 9, 2014. |
| Search Report for Application No. GB1403472.2, dated Aug. 22, 2014. |
| Search Report for Application No. GB1403474.8, dated Aug. 26, 2014. |
| Search Report for Application No. GB1403475.5, dated Sep. 3, 2014. |
| Search Report for Application No. GB1403476.3, dated Aug. 27, 2014. |
| Search Report for Application No. GB1403477.1, dated Aug. 28, 2014. |
| Search Report for Application No. GB1403478.9, dated Aug. 21, 2014. |
| Search Report for Application No. GB1403480.5, dated Aug. 28, 2014. |
| Search Report for Application No. GB1403615.6, dated Aug. 18, 2014. |
| Search Report for Application No. GB1403616.4, dated Sep. 1, 2014. |
| U.S. Appl. No. 14/212,411, filed Mar. 14, 2014, “Determining Associations and Alignments of Process Elements and Measurements in a Process”. |
| U.S. Appl. No. 14/506,863, filed Oct. 6, 2014, “Streaming Data for Analytics in Process Control Systems”. |
| U.S. Appl. No. 14/507,252, filed Oct. 6, 2014, “Automatic Signal Processing-Based Learning in a Process Plant”. |
| U.S. Appl. No. 62/060,408, filed Oct. 6, 2014, “Data Pipeline for Process Control System Analytics”. |
| U.S. Appl. No. 14/212,493, entitled “Distributed Big Data in a Process Control System”, filed Mar. 14, 2014, 61 pages. |
| Communication Relating to the Results of the Partial International Search, dated Jul. 11, 2014. |
| International Search Report and Written Opinion for Application No. PCT/US2014/030627, dated Sep. 11, 2014. |
| U.S. Appl. No. 13/784,041, filed Mar. 4, 2013. |
| U.S. Appl. No. 14/028,785, filed Sep. 17, 2013. |
| U.S. Appl. No. 14/028,897, filed Sep. 17, 2013. |
| U.S. Appl. No. 14/028,913, filed Sep. 17, 2013. |
| U.S. Appl. No. 14/028,921, filed Sep. 17, 2013. |
| U.S. Appl. No. 14/028,923, filed Sep. 17, 2013. |
| U.S. Appl. No. 14/028,964, filed Sep. 17, 2013. |
| Examination Report for Application No. EP 14724871.0, dated Aug. 17, 2016. |
| Bassat et al., “Workflow Management Combined with Diagnostic and Repair Expert System Tools for Maintenance Operations,” IEEE, pp. 367-375 (1993). |
| Search Report for Application No. GB1517034.3, dated May 26, 2016. |
| Search Report for Application No. GB1517038.4, dated Mar. 22, 2016. |
| Search Report for Application No. GB1501042.4, dated Feb. 2, 2016. |
| Adrian et al., “Model Predictive Control of Integrated Unit Operations Control of a Divided Wall Column,” Chemical Engineering and Processing: Process Information, 43(3):347-355 (2004). |
| Daniel et al., “Conceptual Design of Reactive Dividing Wall Columns,” Symposium Series No. 152, pp. 364-372 (2006). |
| Dejanovic et al., “Conceptual Design and Comparison of Four-Products Dividing Wall Columns for Separation of a Multicomponent Aromatics Mixture,” Distillation Absorption, pp. 85-90 (2010). |
| Dongargaonkar et al., “PLC Based Ignition System,” Conference Records of the 1999 IEEE Industry Application Conference, 1380-1387 (1999). |
| Hiller et al., “Multi Objective Optimisation for an Economical Dividing Wall Column Design,” Distillation Absorption, pp. 67-72 (2010). |
| International Preliminary Report on Patentability for Application No. PCT/US2014/030627, dated Sep. 15, 2015. |
| International Preliminary Report on Patentability for Application No. PCT/US2015/020148, dated Sep. 14, 2016. |
| Kiss et al., “A control Perspective on Process Intensification in Dividing-Wall Columns,” Chemical Engineering and Processing: Process Intensification, 50:281-292 (2011). |
| Pendergast et al., “Consider Dividing Wall Columns,” Chemical Processing (2008). Retrieved from the Internet at: URL:http://www.chemicalprocessing.com/articles/2008/245/?show=all. |
| Sander et al., “Methyl Acetate Hydrolysis in a Reactive Divided Wall Column,” Symposium Series No. 152, pp. 353-363 (2006). |
| Schultz et al., “Reduce Costs with Dividing-Wall Columns,” Reactions and Separations, pp. 64-71 (2002). |
| Shah et al., “Multicomponent Distillation Configurations with Large Energy Savings,” Distillation Absorption, pp. 61-66 (2010). |
| Thotla et al., “Cyclohexanol Production from Cyclohexene in a Reactive Divided Wall Column: A Feasibility Study,” Distillation Absorption, pp. 319-324 (2010). |
| Tututi-Avila et al., “Analysis of Multi-Loop Control Structures of Dividing-Wall Distillation Columns Using a Fundamental Model,” Processes, 2:180-199 (2014). |
| U.S. Appl. No. 13/784,041 dated Apr. 6, 2015. |
| U.S. Appl. No. 13/784,041, dated Feb. 26, 2016. |
| U.S. Appl. No. 13/784,041, dated Oct. 15, 2015. |
| Hu et al., “Toward Scalable Systems for Big Data Analytics: A Technology Tutorial,” IEEE, 2:652-687 (2014). |
| Lee et al., “Recent Advances and Trends in Predictive Manufacturing Systems in Big Data Environment,” Manufacturing Letters, 1(1):38-41 (2013). |
| Mandavi et al., “Development of a Simulation-Based Decision Support System for Controlling Stochastic Flexible Job Shop Manufacturing Systems,” Simulation Modeling Practice and Theory, 18:768-786 (2010). |
| Mezmaz et al., “A Parallel Bi-Objective Hybrid Metaheuristic for Energy-Aware Scheduling for Cloud Computing Systems,” Journal of Parallel and Distributed Computing, Elsevier (2011). |
| Notification of First Office Action for Chinese Application No. 201480014734.3, dated Apr. 19, 2017. |
| Razik et al., “The Remote Surveillance Device in Monitoring and Diagnosis of Induction Motor by Using a PDA,” IEEE (2007). |
| Search Report for Application No. GB1617019.3, dated Feb. 27, 2017. |
| Siltanen et al., “Augmented Reality for Plant Lifecycle Management,” IEEE (2007). |
| Xu, “From Cloud Computing to Cloud Manufacturing,” Robotics and Computer-Integrated Manufacturing 28:75-86 (2012). |
| Extended European Search Report for Application No. 17157505.3, dated Jun. 30, 2017. |
| First Office Action for Chinese Application No. 201410088828.7, dated Aug. 1, 2017. |
| First Office Action for Chinese Application No. 201410097873.9, dated Aug. 9, 2017. |
| First Office Action for Chinese Application No. 201410097922.9, dated Aug. 18, 2017. |
| First Office Action for Chinese Application No. 201410097923.3, dated Aug. 28, 2017. |
| First Office Action for Chinese Application No. 201410098326.2, dated Jul. 27, 2017. |
| First Office Action for Chinese Application No. 201410098327.7, dated Jul. 26, 2017. |
| First Office Action for Chinese Application No. 201410098982.2, dated Aug. 9, 2017. |
| First Office Action for Chinese Application No. 201410099103.8, dated Aug. 9, 2017. |
| First Office Action for Chinese Application No. 201410080524.6, dated Sep. 13, 2017. |
| First Office Action for Chinese Application No. 201410097623.5, dated Sep. 26, 2017. |
| First Office Action for Chinese Application No. 201410097874.3, dated Aug. 18, 2017. |
| First Office Action for Chinese Application No. 201410097921.4, dated Oct. 10, 2017. |
| Notice of Reasons for Rejection for Japanese Application No. 2014-051599, dated Nov. 28, 2017. |
| Notification of First Office Action for Chinese Application No. 201410099068.X, dated Sep. 15, 2017. |
| Aouada et al., “Source Detection and Separation in Power Plant Process Monitoring: Application of the Bootstrap,” IEEE International Conference on Acoustics Speech and Signal Processing Proceedings (2006). |
| Bruzzone et al., “Different Modeling and Simulation Approaches Applied to Industrial Process Plants,” Proceedings of the Emerging M&S Applications in Industry & Academia/Modeling and Humanities Symposium (2013). |
| First Office Action for Chinese Application No. 201410097675.2, dated May 10, 2017. |
| International Preliminary Report on Patentability for Application No. PCT/US2015/053931, dated Apr. 11, 2017. |
| Notification of First Office Action for Chinese Application No. 201410097875.8, dated Jul. 7, 2017. |
| Sailer et al., “Attestation-Based Policy Enforcement for Remote Access,” Proceedings of the 11th ACM Conference on Computer and Communications Security (2004). |
| Search Report for Application No. GB1617020.1, dated Apr. 13, 2017. |
| Search Report for Application No. GB1617021.9, dated Apr. 5, 2017. |
| Search Report for Application No. GB1617022.7, dated Apr. 18, 2017. |
| Search Report for Application No. GB1617023.5, dated Apr. 7, 2017. |
| Search Report for Application No. GB16702014.0, dated Aug. 3, 2017. |
| Sunindyo et al., “An Event-Based Empirical Process Analysis Framework,” ESEM (2010). |
| Notice of Reasons for Rejection for Japanese Application No. 2014-041785, dated Dec. 5, 2017. |
| Notice of Reasons for Rejection for Japanese Application No. 2014-041785, dated Nov. 30, 2017. |
| Notice of Reasons for Rejection for Japanese Application No. 2014-048410, dated Dec. 29, 2017. |
| Notice of Reasons for Rejection for Japanese Application No. 2014-048411, dated Dec. 5, 2017. |
| Notice of Reasons for Rejection for Japanese Application No. 2014-048412, dated Feb. 27, 2018. |
| Notice of Reasons for Rejection for Japanese Application No. 2014-049916, dated Feb. 27, 2018. |
| Notice of Reasons for Rejection for Japanese Application No. 2014-049917, dated Mar. 6, 2018. |
| Notice of Reasons for Rejection for Japanese Application No. 2014-049918, dated Dec. 12, 2017. |
| Notice of Reasons for Rejection for Japanese Application No. 2014-049919, dated Nov. 29, 2017. |
| Notice of Reasons for Rejection for Japanese Application No. 2014-049920, dated Feb. 20, 2018. |
| Notice of Reasons for Rejection for Japanese Application No. 2014-051114, dated Dec. 28, 2017. |
| Notice of Reasons for Rejection for Japanese Application No. 2014-051595, dated Jan. 16, 2018. |
| Notice of Reasons for Rejection for Japanese Application No. 2014-051596, dated Jan. 16, 2018. |
| Notice of Reasons for Rejection for Japanese Application No. 2014-051596, dated Jan. 9, 2018. |
| Notice of Reasons for Rejection for Japanese Application No. 2014-051597, dated Jan. 9, 2018. |
| Notice of Reasons for Rejection for Japanese Application No. 2014-051598, dated Mar. 13, 2018. |
| Second Office Action for Chinese Application No. 201410097922.9, dated Jan. 9, 2018. |
| Final Rejection for Japanese Application No. 2014-048410, dated May 29, 2018. |
| First Office Action for Chinese Application No. 201410097872.4, dated Aug. 23, 2017. |
| First Office Action for Chinese Application No. 201510049715.0, dated May 4, 2018. |
| Notice of Reasons for Rejection for Japanese Application No. 2014-049915, dated Mar. 13, 2018. |
| Notice of Reasons for Rejection for Japanese Application No. 2014-049918, dated Apr. 10, 2018. |
| Notice of Reasons for Rejection for Japanese Application No. 2016-503431, dated Apr. 3, 2018. |
| Second Office Action for Chinese Application No. 201410088828.7, dated Apr. 27, 2018. |
| Second Office Action for Chinese Application No. 201410097675.2, dated Feb. 11, 2018. |
| Second Office Action for Chinese Application No. 201410097873.9, dated May 15, 2018. |
| Second Office Action for Chinese Application No. 201410097875.8, dated Jun. 6, 2018. |
| Second Office Action for Chinese Application No. 201410098327.7, dated Feb. 27, 2018. |
| Decision of Refusal for Japanese Application No. 2014-048410, dated May 29, 2018. |
| Decision of Rejection for Chinese Application No. 201410097675.2, dated Jul. 2, 2018. |
| Examination Report for Application No. EP 14724871.0, dated Aug. 10, 2018. |
| First Office Action for Chinese Application No. 201510113223.3, dated Jul. 4, 2018. |
| First Office Action for Chinese Application No. 201580014241.4, dated Jun. 22, 2018. |
| Notice of Reasons for Rejection for Japanese Application No. 2014-048411, dated Jul. 31, 2018. |
| Notice of Reasons for Rejection for Japanese Application No. 2014-049919, dated Jul. 31, 2018. |
| Notice of Reasons for Rejection for Japanese Application No. 2014-049920, dated Jun. 5, 2018. |
| Notice of Reasons for Rejection for Japanese Application No. 2014-051595, dated May 29, 2018. |
| Notice of Reasons for Rejection for Japanese Application No. 2014-051596, dated May 29, 2018. |
| Second Office Action for Chinese Application No. 201410097623.5, dated Jun. 26, 2018. |
| Second Office Action for Chinese Application No. 201410097872.4 dated Jul. 12, 2018. |
| Second Office Action for Chinese Application No. 201410097921.4, dated Jul. 5, 2018. |
| Second Office Action for Chinese Application No. 201410098326.2, dated Jun. 19, 2018. |
| Second Office Action for Chinese Application No. 201410098982.2, dated Jun. 11, 2018. |
| Second Office Action for Chinese Application No. 201410099068.X, dated Jun. 14, 2018. |
| Second Office Action for Chinese Application No. 201410099103.8, dated Jun. 5, 2018. |
| Third Office Action for Chinese Application No. 201410097922.9, dated Aug. 3, 2018. |
| Number | Date | Country | |
|---|---|---|---|
| 20140277656 A1 | Sep 2014 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61783112 | Mar 2013 | US |
