Solution Center (Concept)

Solution Center Module Overview

The Solution Center Module serves as the primary entry point and management hub for all FrameworX solutions. It provides centralized control over solution creation, configuration, licensing, and execution, enabling users to manage multiple solutions from a single interface while supporting both local and remote access through desktop and web interfaces.

On this Page:

• Solution Center Module Overview
• Key Concepts
• What It Does
• Configuration Workflow
• Runtime Behavior
• Feature Highlights

Key Concepts

• Solution File (.dbsln): Encrypted SQL database containing all module configurations in a single file
• Solution List: Central display of available solutions with status indicators and preview images
• Server Connection: Access to local or remote solutions via TWebServices (port 10108)
• Multi-User Collaboration: Concurrent engineering on the same solution by multiple users
• Execution Profiles: Development, Validation, or Production modes with different security levels
• Click-Once Deployment: Browser-based Designer launch without local installation

What It Does

• Creates new solutions from scratch or industry-specific templates
• Manages solution lifecycle including backup, import, export, and version control
• Controls licensing for development, runtime, or combined capabilities
• Launches Designer for configuration and Runtime for execution
• Enables remote solution access via web UI or server connections
• Monitors solution status, resource usage, and active connections

Configuration Workflow

Solution Center Configuration Workflow

Feature Highlights

Solution Organization

• Single-file architecture: All configurations in one .dbsln file
• Preview images: MainPage display shown as solution thumbnail
• Multiple views: List, Card, or Table display options
• Search and filter: Quick solution location by name or description
• Folder organization: Logical grouping of related solutions

Collaboration Features

• Multi-user support: Concurrent engineering on same solution
• Server-based access: Centralized solution repository
• Access control: Security keys for remote connections
• Version management: Built-in backup and restore capabilities
• Legacy migration: Upgrade path from .tProj files (v9.1+)

License Management

• Unified licensing: Single point for all license operations
• License types: Development, Runtime, Combined, Trial
• Feature visibility: Tag count, user limits, I/O points
• Remote activation: Online and offline license activation
• Expiration monitoring: Proactive license renewal alerts

Deployment Flexibility

• Click-Once technology: Zero-installation Designer access
• Cross-platform: Windows desktop and web browser support
• Remote management: Full functionality over network
• Backup/restore: Solution portability between systems
• Template library: Industry-specific starting points

Operational Control

• Execution profiles: Separate development and production modes
• Resource monitoring: CPU, memory, and connection tracking
• Service management: Individual module enable/disable
• Diagnostic access: Integrated log viewing and troubleshooting
• Automated startup: Solution auto-launch configuration

Overview

Solution Center is the platform’s home screen and launch point. It lets you create, open, license, and launch solutions, and jump into Designer (configure) or Runtime (execute). It can manage local or remote solutions and supports multi-user collaboration.   

What you can do

• Create/Open solutions (local or remote) and organize them in the Solution List. 

• Launch Designer to edit (or read-only) and start Runtime with the chosen profile (Dev/Validation/Production). 

• Manage licenses (view status, activate) for the connected machine. 

• Backup / Import / Export / Clone solutions for deployment or recovery. 

• Access remote servers via TWebServices (web UI at /solutions, supports ClickOnce Designer launch when available). 

• Upgrade legacy projects (.tProj) to current solutions (.dbsln). 

Key concepts & terms

• Solution file (.dbsln) — encrypted SQL file that stores the whole configuration (tags, alarms, scripts, displays). Backups use .dbback. 

• Solution Center / Solutions Manager — UI names you’ll see for the same entry point. 

• TWebServices — required service for remote access; default port 10108; optional AccessKey in the URL. 

• Profiles — Development, Validation, Production (affect Runtime behavior). 

• License types — Development, Runtime, Combined, Trial. 

How it fits in the platform

Solution Center is the UI environment for solution management & launch: from here you open solutions, configure (Designer), and execute (Runtime). The Platform UI environment table in the overview places SolutionCenter alongside Designer and Runtime. 

Interface at a glance

• Solution List — recent/organized solutions; search, status, views.

• Actions Toolbar — New, Open, Edit, Run, Stop, Backup, Import/Export.

• Information/Properties — solution details, license status, runtime state. 

Configuration at a glance

1. Connect to a server (optional): enter IP/DNS in Server Information; ensure TWebServices is running. Or open the Web UI at http://<server>:10108/solutions. 

2. Create or open: New (blank or template), Import/Clone, or open an existing .dbsln (local/remote). 

3. Edit or run: Edit (Designer; supports ClickOnce from web UI) or Run (choose profile). 

4. License & properties: check/activate license; review execution and advanced settings. 

See also

• Designer Workspace (Concept) — where you configure modules and UI. 

• Runtime & Clients (Concept) — how execution and clients work. 

• Solution Center (Reference) — screens, buttons, and task details. 

Notes on structure (so we’re consistent across modules)

• Keep Overview to 2–4 sentences.

• Use “What you can do” for outcome-oriented bullets (value before UI details).

• Keep UI specifics brief in Interface at a glance; deep details live in Reference.

• Link down to Reference and sideways to Designer and Runtime Concept pages to preserve the mental model.

Designer and Modules (Concept)

Designer Module Overview

The Designer Module provides a unified configuration workspace for all FrameworX solution development. It delivers an integrated environment for design, development, testing, validation, and deployment across all functional modules, organized through the Four Pillars architecture that structures data flow from field connectivity to user visualization.

On this Page:

• Designer Module Overview
• Key Concepts
• What It Does
• Configuration Workflow
• Runtime Behavior
• Feature Highlights

Key Concepts

• Solution File (.dbsln): Encrypted SQL database containing all module configurations and engineering logic
• Modular Architecture: Compartmentalized design with independent modules ensuring isolated changes
• Four Pillars Organization: Logical grouping of modules by function (Foundation, Industrial, Business, Visualization)
• Object Model: .NET-based classes providing inherited properties and methods for all configured objects
• IntelliSense: Context-aware auto-completion for tags, objects, and properties
• Test Mode: In-Designer runtime execution for validation without deployment

What It Does

• Provides unified interface for configuring all solution modules and components
• Enables offline and online configuration with multi-user collaboration support
• Offers integrated testing and validation without leaving the design environment
• Manages cross-references, version control, and change tracking automatically
• Supports refactoring with automatic reference updates throughout solution
• Delivers context-sensitive editing with real-time validation and tooltips

Configuration Workflow

Designer Configuration Workflow

Runtime Behavior

Module Organization by Four Pillars

Pillar 1: Unified Namespace (Foundation)

• Tags: Real-time data points with .NET-based types and properties
• Templates (UDTs): Reusable data structures for complex objects
• Asset Tree: Hierarchical organization matching physical equipment
• TagProviders: Dynamic connections to external data sources

Pillar 2: Process Modules (Industrial Integration)

• Devices: 70+ native drivers, OPC UA/DA, MQTT SparkPlug B support
• Alarms: Condition monitoring, notifications, audit trail
• Historians: Time-series storage with SQL engine, Canary, PI, InfluxDB

Pillar 3: Application Modules (Business Logic)

• Scripts: C#, VB.NET, Python, JavaScript with multi-threading
• Datasets: SQL connections, queries, real-time data tables
• Reports: Text, PDF, HTML5 generation with web services

Pillar 4: User Interface (Visualization)

• Displays: HMI/SCADA screens with responsive design
• Symbols: Reusable graphical components library
• Clients: HTML5, .NET SmartClient, mobile deployment

Designer Workspace Interface

Object Model Integration

All configured objects inherit from .NET classes, providing:

• Native properties and methods without custom coding
• Direct access to .NET functionality (e.g., DateTime.DayOfWeek)
• Runtime statistics (e.g., Script.Task.LastCPUTime)
• Seamless integration with external .NET assemblies

Feature Highlights

Development Productivity

• IntelliSense everywhere: Auto-completion for all tag names and object references
• Real-time validation: Red borders and tooltips for invalid entries
• Refactoring support: Rename objects with automatic reference updates
• Cross-reference tools: Find all uses of any object instantly
• Version control: Built-in change tracking and comparison

Unified Configuration

• Single environment: All modules configured in one interface
• Consistent UI: Same patterns across all configuration tables
• Context menus: Right-click access to relevant operations
• Drag-drop support: Move items between panels and modules
• Keyboard shortcuts: Ctrl+S save, F5 test mode, standard editing

Testing and Validation

• Test Mode: Run solution without leaving Designer
• Online configuration: Modify running solutions safely
• Simulation tools: Test without field devices connected
• Error checking: Automatic validation on save
• Performance monitoring: Real-time resource usage display

Collaboration Features

• Multi-user support: Concurrent engineering on same solution
• Change tracking: Automatic logging of all modifications
• User permissions: Role-based access to configuration areas
• Import/Export: Excel, CSV for bulk operations
• Documentation: Integrated help and examples

Module Integration

• Namespace organization: Logical grouping (Tag, Alarm, Device, Script)
• Shared object model: Consistent properties across modules
• Event-driven updates: Changes propagate automatically
• Unified database: Single SQL store for all configurations
• Cross-module references: Direct linking between components

Designer & Modules (Concept)

Overview

The Designer is the configuration workspace for your solution—where you define tags, devices, datasets, alarms, scripts, displays, and security. It supports offline and online editing in a unified, cross-platform UI. See the workspace layoutsketch on page 1 for the main regions (Navigation Tree, Canvas, Properties, Output). 

What you can do

• Configure UNS/Tags, Devices, Datasets/SQL, Alarms, Scripts, Displays, and Security from a single workspace. 

• Use Test Mode to validate behavior without leaving Designer. 

• Navigate fast via Solution Explorer and quick shortcuts (Home, Tags/UNS, Draw, Runtime). 

• Inspect cross-references, errors, and build output in the bottom panels. 

• Benefit from tooltips, validation, IntelliSense, and refactoring across editors. 

Modules organized by the Four Pillars

Use this model to avoid a long flat list and give users a mental map. (Each item links to its module reference.)

• Define Your Data

  UNS & Tags, Datasets/Queries, Data Explorer tools. 

• Connect & Collect

  Devices (protocol drivers, OPC UA/DA, MQTT Sparkplug B), Connections/Monitors. 

• Monitor & Act

  Alarms (Items/Groups/Areas, Notifications), Historian (SQL/Canary, store-and-forward), Security (users, groups, AD/LDAP). 

• Visualize & Share

  Displays (desktop & web), Reports/Forms/WebData. 

Tip: In the Solution Explorer table (Reference), keep these pillar groupings by section so users can scan: Solution, Runtime, UNS, Devices, Alarms, Historian, Datasets, Reports, Scripts, Security, Displays, Data Explorer, Track Changes. (See page 3 for the full child-page matrix.) 

Key concepts & terms

• Solution (.dbsln): encrypted SQL file storing all configuration. 

• Modular architecture: changes in one module won’t break others. 

• Unified Namespace (UNS): central semantic model for tags and assets. 

How it fits at runtime

Designer produces the configuration your Runtime executes; clients (desktop & web) visualize and interact with the running system. Designer’s Test Mode lets you validate behavior before publishing to Runtime. (See “Runtime execution” and “Display/HMI clients” callouts on page 1.) 

Interface at a glance

• Navigation Tree (modules by pillar) • Design Canvas • Properties Panel • Output/Errors/Cross-Ref. Diagram on page 1. 

• Quick navigation: Home, UNS/Tags, Draw (Displays), Runtime; plus Switch menu to Solution Management, docs, forum, and training. 

Configuration at a glance

1. Open a solution in Designer.

2. Work pillar-by-pillar: Define data → Connect devices → Monitor/Act → Visualize/Share.

3. Run/Test from Designer; then publish to Runtime. 

See also

• Solution Center (Concept): launchpad for create/open/license/run.

• Runtime & Clients (Concept): execution and client connections.

• Designer Environment (Reference): UI details, toolbars, shortcuts, child pages. 

Notes

• This keeps Overview short and moves value into What you can do—the same pattern we used for Solution Center.

• The pillar mapping mirrors the Process/Application modules split and the Define/Setup/Runtime tiles shown in the Designer reference intro image (page 1), making the concept page consistent with the reference UI. 

Want me to generate the matching Modules (Reference) index grouped by the four pillars (with one-line summaries for each module)?

• Designer Workspace (configuration environment)
• All functional modules (Tags, Historian, Security, etc.)
• Development tools

• Runtime execution
• Display/HMI clients (Web, Mobile, Desktop)
• Utilities and tools

The Designer is where you configure your solution: tags, devices, datasets, alarms, scripts, displays, and security. It supports offline and online configuration and a unified, cross-platform UI.

On this page

• What you configure here

• Offline vs. online editing

• Saving & deploying changes (high level)

Workspace Layout

???????????????????????????????????????????????????????????
?  Menu Bar            [File][Edit][View][Tools][Help]    ?
???????????????????????????????????????????????????????????
?              ?                        ?                 ?
?  Navigation  ?     Design Canvas      ?   Properties    ?
?     Tree     ?                        ?     Panel       ?
?              ?   (Context-Sensitive)  ?                 ?
? ? Solution   ?                        ?  Tag: Temp      ?
?   ? UNS      ?                        ?  Type: Float    ?
?     • Tags   ?                        ?  Value: 75.5    ?
?   ? Devices  ?                        ?                 ?
?   ? Displays ?                        ?                 ?
???????????????????????????????????????????????????????????
?  Output Window      [Build][Errors][Search Results]     ?
???????????????????????????????????????????????????????????

Key Designer Features

Navigation Tips

• Double-click items to edit
• Right-click for context menus
• Drag-drop between panels
• Ctrl+S saves current item
• F5 starts test mode

Unified Namespace And Tags

Build real-time data models, like Tags and Templates. Connect seamlessly to external systems using Dynamic ExternalTags for on-demand data connectivity. Asset modeling allows for the creation of a hierarchical view of the data.

Historian

Easily store and access time-series data. Our platform includes an SQL historian engine, Canary Historian, at no extra cost. It seamlessly integrates with other historian tools like OSIsoft PI and InfluxDB. Plus, it offers out-of-the-box store-and-forward functionality.

Security

Control access to project configuration and user security effortlessly. Enable FDA compliance applications, integrate with Active Directory, LDAP, and more for user security. Define access to displays and objects based on user profiles and security groups with ease.

Devices

Access over 60 native communication protocol drivers for PLCs, transmitters, and field devices effortlessly. Our platform fully supports OPC UA and DA for both server and client execution, along with emerging standards like MQTT SparkPlug B.

Alarms

Easily organize Tags into Groups and Areas for setting Alarm conditions, Audit-Trail, and notifications via email, SMS, or voice. Visualize alarms online and in the historian. Store data agnostically on any selected Database provider.

Datasets

Effortlessly handle multiple connections with SQL databases, customize processes with queries, and tailor tables for real-time tag values. Manage recipes and data files in ASCII, UNICODE, or XML formats with ease.

Scripts

Enable powerful server-side and client-side scripting with high performance. Use languages like C#, VB .NET, Python, and JavaScript. Easily develop multi-threading applications with parallel execution and add references to externally developed classes.

Reports

Generate Text (Plain, XML or JSON), PDF, or HTML5 reports directly without relying on external tools. Additionally, utilize web services to interact with external applications or systems. Access, manipulate, and share data using standardized communication protocols like HTTP and RESTful APIs. This facilitates integration with various software systems such as ERP, BI tools, and custom applications, enhancing data sharing and collaboration.

Displays

Effortlessly design User Interface Displays using our advanced drawing tool, featuring a wide range of customizable Symbols and Graphical components. Whether you need a Responsive Dashboard, a traditional Process Diagram, or high-performance SCADA Graphics, we've got you covered. Deploy your displays seamlessly in HTML5 or secure .NET SmartClient to desktop, mobile, or web clients. Enhance user experience with features like Language Localization, dynamic Engineering Units conversion, and dynamic theme color schemes.

Data Explorer

Perform data mining and monitoring from various data sources, including MQTT Brokers, OPC-UA, PLCs and SQL databases.

Track Changes

Automatically maintain a log of Solution configuration changes, cross-reference tables, and Version Control Information.

Modules Namespaces 

Object Model

In most systems, you usually have to go through the hassle of creating Tags or Variables and writing code to display information about what's happening in your application, like how much CPU is being used by the latest task.

Using our platform, things are way simpler. All those things you need to keep track of, like Tags, AlarmGroups, and ScriptTasks, are actually classes that extend from .NET classes. This means that when you configure your project, you get to use all the properties and methods created by our platform, as well as those already built into the .NET classes.

Take the Tag DateTime, for example. In other systems, you'd need to write code and methods to convert strings to DateTime formats or figure out what day of the week a specific date falls on. But with our platform, the DateTime Tag is just an instance of the .NET class DateTime. That means your project can easily tap into all the properties and methods that come with it, right out of the box.

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, tools and objects used in a project are organized in accessible namespaces. Some of main namespaces 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.