Key Concept: UNFIED BY DESIGN
Multiplafrom, WEbAssembly, ALL-moduels, all connects, mult0laugenst
then Follows User Journey: Create → Design → Deploy/Run
Which the main blocks down
the child pages explore tho concepts in 3 child Pages; SOlutnDenter. Desing & ModulesConfig, Runtime DIpalys & Utititlies (or Tools)
Core Components — servers, services, modules; how they fit together.
Workspaces — Solution Center Overview and Designer Workspace (can be siblings or a combined page).
Runtime & Clients — SmartClient/Web, roles, where logic runs.
Our platform relies on the three components described below. It supports distributed architectures, which means that each one of these software components may be running on one computer, exchanging data with the modules on other computers.
Depoloyment models
Our platform provides versatile deployment choices tailored to your operational requirements. Whether you require a straightforward standalone configuration with both server and client components on a single machine or a sophisticated distributed system optimized for slower networks, our platform seamlessly adjusts.
Our platform is adept at managing client and server systems, whether they are networked computers or accessed remotely via WAN or Cloud. Additionally, it facilitates distributed control systems across various plants for real-time monitoring and management. For mission-critical applications, you have the option to deploy redundant servers with automatic failover and data synchronization, ensuring continuous operation.
Unified Designer | |
---|---|
Standalone Configuration
| Distributed Architecture
|
Redundant Systems
| Cloud and Hybrid
|
Our platform supports projects ranging from Edge applications on embedded devices to large-scale distributed applications.
This section covers some standard deployment architectures.
In a Stand-Alone System, all components run on one machine, like a Windows desktop or industrial PC, serving as both server and client. It can also act as an Edge data collector for remote platforms.
In a Distributed Data Acquisition System, a server machine hosts device modules communicating with remote PLCs or historians. The SCADA client can be on the same server or a separate computer. This setup is ideal for plants with devices on slow or limited networks, optimized with I/O servers for better performance.
In a Client and Server System, the platform's server handles server-side modules such as alarms, historians, and data acquisition.
Operator client stations run on other networked or remote computers connected via WAN or Cloud interface.
In a Distributed Control System, multiple servers are set up across different plants or projects, enabling access to control rooms for each. Users select the specific plant they wish to monitor since clients for each plant are not integrated into one machine. This setup features discrete locations with local operators and redundant servers for each site, along with a central control room for simultaneous monitoring of all sites. Each site is represented by a separate cluster comprising primary and standby servers.
The Redundant Server System comprises two separate computers running the platform's servers, with redundancy managed automatically. Simply specify the IP addresses of the primary and secondary stations. Here are some common deployment scenarios:
1. Solutions Manager (Solution Management)
Our platform enables you to create industrial applications for any platform - you can run it on Windows, Linux, Mac, Routers and Universal Robots. This is the first interface you'll see when running the software and it showcases all the solution files you have. You can create, edit, manage and run solutions from here.
2. Designer (Solution Configuration)
The Designer Workspace allows you to edit solutions’ displays and tags, as well as modules such as Devices, Alarms, Scripts, Datasets and Historian.
3. Runtime (Solution Execution)
When you run your solution, the first UI you'll be presented with is the TStartup, which is responsible for loading everything the solution needs. This includes the TServer, which enables communications with databases, and the modules that will act behind the scenes to display the information the user sees. It will also open the User Interface, which can be either Windows or Web Clients.
one-page orientation + high-level diagram; link to pillars and key runtimes.
In a Stand-Alone System, all components run on one machine, like a Windows desktop or industrial PC, serving as both server and client. It can also act as an Edge data collector for remote platforms.
-----
Consolidation to do:
Explore pre-built FrameworX solutions that demonstrate best practices and industry-specific implementations. These examples range from quick 15-minute demos to complete industry templates, providing practical starting points for your own solutions. All examples include full source code and can be modified to match your specific requirements.
A complete craft brewery automation system demonstrating batch processing, recipe management, and quality control.
Key Features:
Technologies Demonstrated:
Download & Run Time: 15 minutes
End-to-end production line monitoring with real-time KPIs, downtime tracking, and predictive maintenance.
Key Features:
Technologies Demonstrated:
Download & Run Time: 20 minutes
Smart building control system with HVAC, lighting, access control, and energy optimization.
Key Features:
Technologies Demonstrated:
Download & Run Time: 15 minutes
Complete automotive plant solution following AIAG standards with MES integration.
Included Modules:
Pre-configured Components:
Compliance & Standards:
GAMP5-compliant solution for food processing with full traceability.
Included Modules:
Pre-configured Components:
Integration Examples:
SCADA solution for municipal water systems with EPA reporting.
Included Modules:
Pre-configured Components:
Compliance Features:
Multi-site energy monitoring with ISO 50001 compliance tools.
Included Modules:
Pre-configured Components:
Standards Support:
Single-server solution ideal for small to medium applications.
Example Configuration:
Use Cases:
Deployment Time: 2 hours
Hot-standby configuration with automatic failover for mission-critical applications.
Example Configuration:
Use Cases:
Key Features:
Multi-site deployment with central monitoring and local autonomy.
Example Configuration:
Use Cases:
Architecture Components:
Hybrid architecture combining on-premise control with cloud analytics.
Example Configuration:
Use Cases:
Cloud Services Integration:
<details> <summary>Structured Information for AI Tools</summary>
json
{
"module": "Solution Examples",
"category": "Learning Resources",
"examples": {
"quickDemos": ["Brewery", "Manufacturing Line", "Building Management"],
"industryTemplates": ["Automotive", "Food & Beverage", "Water/Wastewater", "Energy"],
"architecturePatterns": ["Standalone", "Redundant", "Distributed", "Cloud"]
},
"typicalTimeToImplement": {
"quickDemo": "15-20 minutes",
"industryTemplate": "2-4 hours",
"customSolution": "1-4 weeks"
},
"keyLearningObjectives": [
"Understand FrameworX capabilities",
"Learn industry best practices",
"See architecture patterns",
"Accelerate solution development"
],
"commonCustomizations": [
"Device connection settings",
"Tag naming conventions",
"Display branding",
"Report formats",
"Security configuration"
],
"downloadLocation": "Solutions Manager > File > Import Solution"
}
</details>