Our flexible product family and licensing options let you choose exactly what you need—from lightweight edge connectivity and Machine HMIs to full-scale deployments with FrameworX Unlimited. Available as perpetual or subscription licenses.
On this page:
FrameworX Unlimited comes complete with unlimited clients, I/O and development, a server-based platform with all the tools you need. But if you'd like to have something that more closely fits the size of your application, we also offer three additional product families:
FrameworX Unlimited delivers an enabling platform for limitless real-time, scalable edge-to-cloud solutions.
FrameworX Unlimited | |
---|---|
For Enterprise solutions. | |
Everything included on FactoryStudio and more. | |
Unlimited Clients (Windows WPF, .NET SmartClients, Web HTML5, Mobile). | |
Unlimited Points IO. | |
Unlimited Drivers. | |
Unlimited features — in practice, the only limit is your hardware. |
Product Models | |
---|---|
Unlimited | Unlimited Tags, Unlimited Drivers and Points, Unlimited Users. |
FrameworX FactoryStudio is our family of software products designed to enable cost-effective deployments is smaller applications. It has all the functionality of the FrameworX Unlimited, except by the number of process tags and remote client connections.
FactoryStudio | |
---|---|
Powerful and flexible tool for data collection and management, dashboard and report creation, and more. | |
Everything included on MachineHMI and EdgeConnect and more. | |
Scalable, by the IO number & clients. | |
70+ drivers included at no extra cost. | |
Advanced scripting: C#, VB.NET, Python. | |
Redundancy available. | |
SDK Extensions/Toolkits included. |
Product Models | |
---|---|
Model | Client Connections |
15000 Process Tags | 25 |
5000 Process Tags | 10 |
1500 Process Tags | 10 |
500 Process Tags | 3 |
150 Process Tags | 3 |
Process tags are the variables in the solution that have connection with the process, by using either the Device Module, the TagProvider module, or used by Alarms or Historian module. If a tag is used across multiple modules—for example, acquired from a PLC using the Devices module and also used in Alarms and Historian—it only counts once.
The Client Connections are the number Operators connected with the solution running from any device (Desktop or Mobile, Native Windows or Web). This number is related to Runtime connections, it doesn't include engineering configuration connections, which are unrestricted. Additional Client License packages may be added to the licensing.
FrameworX MachineHMI is our family of software products designed for Machine Panel replacement, operator interfaces at the network edge, on the factory floor, or in embedded OEM devices.
MachineHMI | |
---|---|
Connect with drivers and PLCs, build HMIs, and more. | |
Everything included on EdgeGateway and more: | |
Scalable, by the IO number & clients. | |
70+ drivers included at no extra cost. | |
Build Graphical Displays for User Interface. | |
Thousands of Symbols. | |
8 different channels for any model, as the number of points is limited to 1500, in practice this is also a hard limit to reach. |
Product Models | |
---|---|
Model | Data Connections |
1500 Process Tags | 2 |
500 Process Tags | 2 |
150 Process Tags | 2 |
Process tags are the variables in the solution that have connection with the process, by using either the Device Module, the TagProvider module, or used by Alarms or Historian module. If a tags is used inI multiple modules, for instance get from the PLC using Devices, and use in Alarms and Historian, that is counting only one time.
The MachineHMI product family allows 2 runtime client connections. One connection is the main Operator Displays (whatever is local or remote), the second one is to remote use of the solution.
FrameworX EdgeConnect is designed for IIoT applications and can be embedded in field or OEM devices at the edge of the network.
EdgeConnect | |
---|---|
Embedded device communications and processing at the edge or as flexible secure gateway | |
70+ drivers included at no extra cost (Premium protocols charged). | |
OPC UA Client/Server and MQTT Client / Broker | |
SQL connections (DataServer Model) | |
Device Redundancy available | |
Scripts (C#, VB.Net and Python) |
Product Models | |
---|---|
Model | Data Connections |
DataServer | Unlimited. |
DataGateway | One northbound (Business Layer) connection, unlimited southbound (Field Layer) connections. |
DataCollector | One northbound connection and read-only connections with the field devices. |
FrameworX DataServer transforms a field device into a fully enabled multi-protocol edge data server, including an MQTT Broker and OPC UA Server. It supports .NET and Python scripting , data synchronization with read-write access at the edge, access to SQL Databases, connection with FrameworX servers, Historian Tools like Canary, or Enterprise cloud solutions, like Azure or SnowFlake, or MES systems.
Typical applications include OPC Server replacement, MQTT Broker at the edge, with unlimited device connections and extended features (Scripts, SQL, WebServices, Remote Engineering).
FrameworX DataGateway enables multiple Protocols Read/Write for protocol converter, bridge tunneling, data normalization or calculation at the edge. Compared to the DataServer, it restricts SQL access and allows one Northbound Connection, meaning the OPC Server, or the built-in MQTT Brokers, and the TagProviders, will serve data to only on server, or hot-standby pair or servers. The Field devices protocols, are unrestricted to read and write to any device.
Typical applications include OPC Server replacement, MQTT Broker at the edge, unlimited device connections with extended features (Scripts, WebServices, Remote Engineering).
Framework DataCollector provides a low-cost solution to data-acquisition and integration other systems, like FrameworX servers, Historian products, MES applications, and others. Comparing with the DataGateway, it allow has one Northbound connection, but the connection with the field devices are read-only.
Typical applications include getting data to to publish up to Historians, MQTT Brokers, OPC UA servers, FrameworX UNS Servers, or other product custom integration. The scripts running at the device, allows data normalization and aggregation at the edge.