Introduction to FrameworX Modules
The versatility of our platform arises from its rapid application development tools and a comprehensive suite of integrated modules, designed to cater to diverse industrial applications, ranging from Edge to SCADA HMI and Enterprise systems.
On this page:
| Table of Contents | ||
|---|---|---|
|
Flexible Architecture
The platform's architecture enables you to develop in a single environment and deploy the necessary components from the server to the edge, based on your requirements. The modular architecture provides a more flexible and scalable solution for automation and control applications, allowing faster development, simplified maintenance, and enhanced adaptability to changing requirements.
The platform has a complete set of Rapid Application Development tools.
Included Modules
Modules are organized to deliver a simple way to encapsulate all the functionalities required when creating real-time industrial applications, from Edge to SCADA HMI and Enterprise systems.
Tags, Assets and Templates
Creates Real-Time data models, including Tags and Templates. Dynamic tagless on-demand data connectivity with an external system is possible with the Dynamic TagProvider. Asset modeling enables the creation of a hierarchical view of the data.
Tag Historian
Stores and retrieves time-series data. The platform has an SQL historian engine with Canary Historian at no extra charge. Seamless integration with other historian tools, such as OSIsoft PI and InfluxDB. Out-of-the-box-store-and-forward functionality.
Security
Manages access control to the project configuration and security model to the user of the running project. User security allows FDA compliance applications, Active Directory integration, LDAP, and more. Easily define which display/objects are accessible based on the user profile and security groups.
Devices
Includes more than 50 native communication protocol drivers for PLC, transmitters, and field devices. Supports OPC UA and DA, server, and client execution, and new industry standards like MQTT SparkPlug B.
Alarms
Organizes the Tags around Groups and Areas, allowing easy setting for Alarm conditions, Audit-Trail, email or SMS or voice notification, online and historian alarms visualization. Agnostic storage on any selected Database provider.
Datasets
Manages multiple simultaneous connections with SQL database, processes with queries, and tables customized for the values of real-time tags. Manages recipes and data files in ASCII, UNICODE, or XML.
Scripts
Delivers high-performance server-side and client-side scripting capability. Programming languages include C#, VB .NET, Python, and JavaScript. Easily create multi-threading applications with parallel execution for the task and add references to externally developed classes.
Displays
State-of-the-art drawing tool used to create User Interface Displays, with an extensive set of fully customizable Symbols and Graphical components. Create a Responsive Dashboard and a traditional Process Diagram or SCADA High-Performance Graphics. Deploy the displays in HTML5, or secure .NET SmartClient, to desktop mobile or web clients. Extend the user experience with advanced features, including Language Localization, dynamic conversion of Engineering Units, and Displays' dynamic scheme of Theme colors.
Data Explorer
The DataExplorer tools allow you to easily perform data mining and monitoring from various data sources, including MQTT Brokers, OPC-UA, PLCs and SQL databases.
Object Model and Namespaces
Object Model
Most systems require creating a Tag or Variable or writing some code with methods to display information about the running objects in the application, like presenting the CPU consumption of the last task executed, for instance.
In our platform, all execution objects, such as Tags, AlarmGroups, and ScriptTasks, are classes that extend from .NET classes. As such, the project configuration leverages all the properties and methods created by FrameworX and those inherent to the foundational .NET classes.
A simple example is the Tag DateTime. In other systems, there is always code and methods to convert strings to DateTime formats or to find out the day of the week of a specific date. Thanks to the object model, the DateTime Tags is an instance of the .NET class DateTimeh, so the project can access out-of-box all its properties and methods.
Examples
Finding the weekday of date time event: simply access the property Tag.DateTimeExample.Value.DayOfWeek,
Finding the amount of CPU used the last time a calculation was executed: simply access the property Script.Task.Example1.LastCPUTime
Namespaces
All the Modules and objects used in a project are organized in accessible namespaces. Some of main name spaces are:
Tags: group of variables of the real-time database
Alarms: provides access to all information about the management of Alarms.
Devices: includes information on all field devices and its communication status.
In this section...
| Page Tree | ||||
|---|---|---|---|---|
|