US-12625709-B2 - Defining an action on an external application based on a machine learning model prediction from within a data pipeline
Abstract
A data pipeline configuration system allows industrial data pipelines to be configured using an intuitive visual interface. The pipeline configuration system allows graphical pipeline components representing data sources, data processing, analytic or machine learning models, and emitters to be selectively added to an industrial data pipeline application by selecting these components from a library. The pipeline configuration application is created by arranging and linking these selected pipeline components within a pipeline builder section of the configuration system's visual design interface. The design interface also allows analytic or machine learning models to be easily integrated into the pipeline application and mapped to incoming data items, such that the model is applied and scored against incoming data during pipeline operation. The configuration system also allows the user to configure destinations or data sinks for the pipeline data, including both the incoming industrial data and model scoring results.
Inventors
- SOUMENDU CHAKRABORTY
Assignees
- ROCKWELL AUTOMATION TECHNOLOGIES, INC.
Dates
- Publication Date
- 20260512
- Application Date
- 20210701
Claims (20)
- 1 . A system, comprising: a memory that stores executable components; and a processor, operatively coupled to the memory, that executes the executable components, the executable components comprising: a user interface component configured to render an interface display and to receive, via interaction with the interface display, pipeline configuration input that defines aspects of a data pipeline; and a pipeline configuration component configured to generate pipeline application data based on the pipeline configuration input, the pipeline application data configured to execute on a hardware device to implement the data pipeline, wherein the pipeline configuration input comprises at least emitter configuration input that selects, from a library of pipeline components, an emitter component for inclusion in the pipeline application data, wherein the emitter component represents a data sink entity to which output data of the data pipeline is to be published, the library of pipeline components comprises multiple emitter components representing respective different types of data sink entities, and the different types of data sink entities comprise at least an industrial control application and an analytic application, the user interface component is further configured to, in response to selection of an icon representing the emitter component, display an emitter configuration display that renders configurable properties of the emitter component, wherein the configurable properties comprise at least an action property defining an action to be taken by the data sink entity based on values of the output data, and the action property is a function of a type of the data sink entity represented by the emitter component, and the inclusion of the emitter component in the pipeline application data configures the data pipeline to publish the output data and information specifying the action defined by the action property to the data sink entity in accordance with values of the configurable properties.
- 2 . The system of claim 1 , wherein the interface display comprises a component selection section that renders the library of pipeline components as selectable icons, and a pipeline builder section that renders a subset of the icons representing pipeline components selected from the component selection section by the pipeline configuration input, and the pipeline configuration component is configured to generate the pipeline application data based on an arrangement of the subset of the icons in the pipeline builder section and the values of the configurable properties.
- 3 . The system of claim 2 , wherein the emitter configuration input further sets a value of one or more of the configurable properties via interaction with the emitter configuration display.
- 4 . The system of claim 3 , wherein the configurable properties further comprise at least a communication path to the data sink entity.
- 5 . The system of claim 3 , wherein the emitter configuration display renders a list of writable properties of the data sink entity represented by the emitter component, and input fields respectively corresponding to the writable properties, the emitter configuration input comprises a selection of an item of the output data via interaction with one of the input fields, and the selection of the item of the output data by the emitter configuration input maps the item of the output data to one of the writable properties of the data sink entity corresponding to the one of the input fields.
- 6 . The system of claim 5 , wherein an input field, of the input fields, lists output data items available to be selectively mapped to the one of the writable properties of the data sink entity, and the user interface component determines the output data items to be listed in the input field based on a data source for the data pipeline specified by the pipeline configuration input.
- 7 . The system of claim 5 , wherein the input fields are first input fields, and the pipeline configuration input further comprises model selection input that selects an analytic or machine learning model for inclusion in the pipeline application data, and mapping input that maps selected items of input data from a data source to corresponding second input fields of the analytic or machine learning model, and inclusion of the analytic or machine learning model in the pipeline application data configures the data pipeline to apply the analytic model to the selected items of the input data in accordance with the pipeline configuration input.
- 8 . The system of claim 7 , wherein the item of the output data mapped to the one of the writable properties is an analytic result generated by the analytic or machine learning model as a result of applying the analytic model to the selected items of the input data.
- 9 . The system of claim 1 , wherein the different types of data sink entities further comprise at least one of a data repository, a cloud storage platform, a messaging system, a notification system, an industrial control system, a digital asset model, or a digital twin of an industrial asset or industrial system.
- 10 . The system of claim 1 , further comprising a pipeline deployment component configured to deploy the pipeline application to the hardware platform.
- 11 . A method, comprising: rendering, by a system comprising a processor, an interface display on a client device; receiving, by the system via interaction with the interface display, pipeline configuration input that defines aspects of a data pipeline, wherein the receiving comprises: receiving at least emitter configuration input that selects an emitter component, from a library of pipeline components, for inclusion in the data pipeline, wherein the emitter component represents a data sink entity to which output data of the data pipeline is to be published, the library of pipeline components comprises multiple emitter components representing respective different types of data sink entities, and the different types of data sink entities comprise at least an industrial control application and an analytic application; in response to selection of an icon representing the emitter component, displaying, by the system, an emitter configuration display that renders configurable properties of the emitter component, wherein the configurable properties comprise at least an action property defining an action to be taken by the data sink entity based on values of the output data, and the action property is a function of a type of the data sink entity represented by the emitter component; setting, by the system, a value of the one or more of the configurable properties In accordance with the emitter configuration input; and generating, by the system, a data pipeline application in accordance with the pipeline configuration input, wherein the generating comprises configuring the data pipeline application to publish the output data and information identifying the action defined by the action property to the data sink entity in accordance with the emitter configuration input, and the data pipeline application is configured to execute on a hardware platform to implement the data pipeline.
- 12 . The method of claim 11 , wherein the rendering of the interface display comprises formatting the interface display to include a component selection section that renders the library of pipeline components as selectable icons representing the pipeline components, and a pipeline builder section that renders icons representing pipeline components selected from the component selection section by the pipeline configuration input, and the generating of the data pipeline application comprises generating the data pipeline application based on an arrangement of the icons in the pipeline builder section.
- 13 . The method of claim 11 , wherein the setting of the value comprises setting a communication path to the data sink entity.
- 14 . The method of claim 11 , wherein the displaying of the emitter configuration display comprises: rendering a list of writable properties of the data sink entity represented by the emitter component, and rendering input fields respectively corresponding to the writable properties, the emitter configuration input comprises a selection of an item of the output data via interaction with one of the input fields, and the method further comprises: in response to the selection of the item of the output data by the emitter configuration input, mapping, by the system, the item of the output data to one of the writable properties of the data sink entity corresponding to the one of the input fields.
- 15 . The method of claim 14 , wherein the rendering of the input fields comprises: determining pipeline output data items available to be mapped to the data sink entity based on a data source for the data pipeline specified by the pipeline configuration input, and listing, in an input field of the input fields, the pipeline data output items.
- 16 . The method of claim 14 , wherein the input fields are first input fields, and the receiving of the pipeline configuration input further comprises: receiving at least one model selection input that selects an analytic or machine learning model to be included in the data pipeline, and receiving mapping input that maps selected items of input data from a data source to respective second input fields of the analytic or machine learning model, and the generating of the data pipeline application comprises, based on the model selection and the mapping input, configuring the data pipeline application to apply the analytic or machine learning model to the selected items of the input data.
- 17 . The method of claim 16 , wherein the item of the output data mapped to the one of the writable properties is an analytic result generated by the analytic model as a result of applying the analytic model to the selected items of the input data.
- 18 . The method of claim 11 , wherein the different types of data sink entities further comprise at least one of a data repository, a cloud storage platform, a messaging system, a notification system, an industrial control system, the digital asset model, or a digital twin of an industrial asset or industrial system.
- 19 . A non-transitory computer-readable medium having stored thereon instructions that, in response to execution, cause a system comprising a processor to perform operations, the operations comprising: rendering an interface display on a client device; receiving, via interaction with the interface display, pipeline configuration input that defines aspects of a data pipeline, wherein the receiving comprises: receiving at least emitter configuration input that selects an emitter component, from a library of pipeline components, for inclusion in the data pipeline, wherein the emitter component represents a data sink entity to which output data of the data pipeline is to be published, the library of pipeline components comprises multiple emitter components representing respective different types of data sink entities, and the different types of data sink entities comprise at least an industrial control application and an analytic application; in response to selection of an icon representing the emitter component, displaying an emitter configuration display that renders configurable properties of the emitter component, wherein the configurable properties comprise at least an action property defining an action to be taken by the data sink entity based on values of the output data, and the action property is a function of a type of the data sink entity represented by the emitter component; setting a value of the one or more of the configurable properties in accordance with the emitter configuration input; and generating, by the system, a data pipeline application in accordance with the pipeline configuration input, wherein the generating comprises configuring the data pipeline application to publish the output data and information specifying the action defined by the action property to the data sink entity in accordance with the emitter configuration input, and the data pipeline application is configured to execute on a hardware device to execute the data pipeline.
- 20 . The non-transitory computer-readable medium of claim 19 , wherein the different types of data sink entities further comprise at least one of a data repository, a cloud storage platform, a messaging system, a notification system, an industrial control system, the digital asset model, or a digital twin of an industrial asset or industrial system.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to U.S. Provisional Patent Application Ser. No. 63/164,786, filed on Mar. 23, 2021, and entitled “INDUSTRIAL DATA PIPELINE CONFIGURATION SYSTEM,” the entirety of which is incorporated herein by reference. BACKGROUND The subject matter disclosed herein relates generally to industrial data processing and transformation, and, for example, to the configuration of data pipelines BRIEF DESCRIPTION The following presents a simplified summary in order to provide a basic understanding of some aspects described herein. This summary is not an extensive overview nor is it intended to identify key/critical elements or to delineate the scope of the various aspects described herein. Its sole purpose is to present some concepts in a simplified form as a prelude to the more detailed description that is presented later. In one or more embodiments, a system is provided, comprising a user interface component configured to render an interface display and to receive, via interaction with the interface display, pipeline configuration input that defines aspects of an industrial data pipeline; and pipeline configuration component configured to generate pipeline application data based on the pipeline configuration input, the pipeline application data configured to execute on a hardware device to implement the industrial data pipeline, wherein the pipeline configuration input comprises at least emitter configuration input that selects an emitter component, from a library of pipeline components, for inclusion in the pipeline application data, the emitter component representing a data sink entity to which output data of the industrial data pipeline is to be published, and inclusion of the emitter component in the pipeline configuration application data configures the industrial data pipeline to publish the output data to the data sink entity in accordance with the emitter configuration input. Also, one or more embodiments provide a method, comprising rendering, by a system comprising a processor, an interface display on a client device; receiving, by the system via interaction with the interface display, pipeline configuration input that defines aspects of an industrial data pipeline, wherein the receiving comprises: receiving at least emitter configuration input that selects an emitter component, from a library of pipeline components, for inclusion in the industrial data pipeline, the emitter component representing a data sink entity to which output data of the industrial data pipeline is to be published; and generating, by the system, a data pipeline application in accordance with the pipeline configuration input, wherein the generating comprises configuring the data pipeline application to publish the output data to the data sink entity in accordance with the emitter configuration input, and the data pipeline application is configured to execute on a hardware platform to implement the industrial data pipeline. Also, according to one or more embodiments, a non-transitory computer-readable medium is provided having stored thereon instructions that, in response to execution, cause a system comprising a processor to perform operations, the operations comprising rendering an interface display on a client device; receiving, via interaction with the interface display, pipeline configuration input that defines aspects of an industrial data pipeline, wherein the receiving comprises: receiving at least emitter configuration input that selects an emitter component, from a library of pipeline components, for inclusion in the industrial data pipeline, the emitter component representing a data sink entity to which output data of the industrial data pipeline is to be published; and generating, by the system, a data pipeline application in accordance with the pipeline configuration input, wherein the generating comprises configuring the data pipeline application to publish the output data to the data sink entity in accordance with the emitter configuration input, and the data pipeline application is configured to execute on a hardware device to execute the industrial data pipeline. To the accomplishment of the foregoing and related ends, certain illustrative aspects are described herein in connection with the following description and the annexed drawings. These aspects are indicative of various ways which can be practiced, all of which are intended to be covered herein. Other advantages and novel features may become apparent from the following detailed description when considered in conjunction with the drawings. BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a block diagram of an example industrial control environment within a plant operational technology (OT) network in conjunction with representative components of an information technology (IT) network. FIG. 2 is a block diagram of a pipeline configuration system. FIG. 3 is a diagram illustrating a generalized data pipeline t