Abstract:
Exemplified herein is a graphical user interface for an industrial automation system that provides, in a single aggregated and eloquent view, a configuration workspace to discover and present configuration details of control components within an industrial automation system. These components may include industrial controllers, programmable logic controllers (PLCs), supervisory control and data acquisition (SCADA) systems, programmable automation controllers (PACs), and the like, which have modules (as well as submodules) connected thereto. Among other things, the configuration workspace enables a holistic view of identified hardware configuration and the modular reconciliation and troubleshoot of the network device and module configurations.
Abstract:
An industrial control system is provided that includes an application module with machine-readable instructions in a first format. The instructions specify inputs, outputs, processing, or any combination thereof, relating to a process of the industrial control system. The industrial control system also includes a conversion server with a processor that creates a platform-specific application by converting the application module in the first format to a second format that is understandable by a common computing platform of the industrial control system.
Abstract:
The exemplified methods and systems facilitates the configuring of IO devices and its IO modules (and submodules) in enabling an operator to retrieve, via a single input, in a development workspace, a list of IO modules and submodules that is compatible to a given IO device. The exemplified methods and systems facilitates retrieval of compatible IO modules and submodules based parameters of the IO modules and submodules. The exemplified methods and systems provide an intuitive interface, in a development workspace for configuring an IO device, to add a retrieved (i.e., searched) module or submodule from a list thereof to an existing project for a given IO device.
Abstract:
A system includes a first processor configured to intake a schema definition file. The schema definition file defines a set of rules that a data document must follow. The processor extracts one or more data adherence rules from the schema definition file and stores the extracted data adherence rules. Accordingly, subsequent data generation, configuration and/or validation of one or more system data objects may occur without requiring the creation of the data document.
Abstract:
A system includes a first processor configured to intake a schema definition file. The schema definition file defines a set of rules that a data document must follow. The processor extracts one or more data adherence rules from the schema definition file and stores the extracted data adherence rules. Accordingly, subsequent data generation, configuration and/or validation of one or more system data objects may occur without requiring the creation of the data document.
Abstract:
Certain embodiments may include systems and methods for presenting data associated with a power plant configuration tool. In one embodiment, a method may include creating configurations of inter-object relationships among a plurality of asset objects of a massive object model, loading the object model, changing values of data member attributes of at least one of the asset objects with a plant configuration tool without changing software code of plant configuration tool, saving the configurations in a permanent storage location, and retrieving the configurations for display to a user.