Fisher-rosemount Systems, Inc

Peter Hartmann

Mark J Nixon

Anthony Amaro, Jr

John Mark Caldwell

Claudio Fayad

Robert G Halgren, Iii

Richard Clarence Dayo Fabros

Gary Keith Law

Trevor Duncan Schleiss

Seshatre Natarajan

Mariana C Dionisio

Benjamin J Jackman

Mary Grace Francisco

To provide enhanced search capabilities in a process control system, a knowledge repository is generated that includes both contextual data and time series data. The contextual data organizes process plant-related data according to semantic relations between the process plant-related data and the process plant entities. When a user submits a process plant search query related to process plant entities within a process plant, search results are obtained by identifying a data set from the knowledge repository. The contextual data categorizes process parameters so that users can search for a particular process parameter category. Users can tag previous searches to execute them once again at a later time. Users can also execute queries for predicted or future states of process plant entities, batch queries regarding batch processes, soft sensor analytics and monitoring applications, parameter lifecycle applications, perturbation applications, step testing applications, or batch provisioning and scheduling applications using the knowledge repository.

Smart search UI

A distributed control system (DCS) of an industrial process plant includes a data center storing a plant information model that includes a description of physical components, the control framework, and the control network of the plant using a modeling language. A set of exposed APIs provides DCS applications access to the model, and to an optional generic framework of the data center which stores basic structures and functions from which the DCS may automatically generate other structures and functions to populate the model and to automatically create various applications and routines utilized during run-time operations of the DCS and plant. Upon initialization, the DCS may automatically sense the I/O types of its interface ports, detect communicatively connected physical components within the plant, and automatically populate the plant information model accordingly. The DCS may optionally automatically generate related control routines and/or I/O data delivery mechanisms, HMI routines, and the like.

Industrial process control system as a data center of an industrial process plant

To provide search capabilities in a process control system, a contextual knowledge repository is generated that organizes process plant-related data according to semantic relations between the process plant-related data and the process plant entities. When a user submits a process plant search query related to process plant entities within a process plant, search results are obtained by identifying a data set from the contextual knowledge repository which is responsive to the process plant search query. The search results are then presented on a user interface device based on the identified data set. To allow for searches to be performed by user interface devices external to the process plant, a data diode is disposed between a field-facing component and an edge-facing component of the process plant so that data flows from the field-facing component to the edge-facing component without flowing from the edge-facing component to the field-facing component.

Smart search capabilities in a process control system

Search results display in a process control system

Presentation of process control information within a vehicle

An edge gateway system securely delivers and exposes data generated by and/or related to a process plant for consumption by external systems, and includes a field-facing component that sends, to an edge-facing component of the system, a collection of data types defined based on configurations of the process plant and represented using a syntax that is native to the one or more external systems. The field-facing component streams process plant-related content data indicated by one or more interest lists to the edge-facing component, where the streamed data is expressed using the collection of data types. Each interest list may include multiple types of data (e.g., control, I/O, diagnostic, device, historical, etc.) that collectively represent a particular named entity of the plant. Accordingly, the streamed data is securely delivered and exposed, via the edge-facing component, to the external systems.

Edge gateway system with data typing for secured process plant data delivery

An edge gateway system securely delivers and exposes data generated by and/or related to a process plant for consumption by external systems, and includes an edge-facing component that receives process plant-related data from a process plant via a field-facing component of the system. The received data may comport with an exposable data type system utilizing a syntax known to the external systems. The edge-facing component stores the received data in a data lake, and mines the data lake to thereby discover relationships between stored data points. Indications of the received data and the discovered interrelationships are stored in a contextualized process plant knowledge repository, such as a graph database, that is accessible to the external systems and other systems and applications via one or more access mechanisms, which may include utilities, services, servers, and/or applications. Some of the access mechanisms allow external applications to be installed at the edge-facing component.

Edge gateway system with contextualized process plant knowledge repository

An edge gateway system securely delivers and exposes data generated by and/or related to a process plant for consumption by external systems, and includes a field-facing component that stores interest lists indicating the particular data that is allowed to be exposed by the field-facing component. Each interest list is defined (e.g., manually and/or automatically) in accordance with an exposable data type system extracted from (in some cases, multiple different) configurations of the process plant, and may include multiple types of data (e.g., control, I/O, diagnostic, device, historical, etc.) that collectively represent a particular named entity of the plant. The field-facing component obtains the process plant-related data indicated by the interest lists, and provides the obtained field content data to an edge-facing component of the edge gateway system for exposure to external systems, for example, by streaming and/or publishing the obtained data to the edge-facing component.

Growing community of inventors

Austin, TX, United States of America

Peter Hartmann