AccessType (Device AccessType)
Per-point read/write policy for device data, including polling behavior and permissions.
AlarmArea
Hierarchical grouping of AlarmGroups (can have children) to organize large alarm systems.
AlarmGroup
Collection of AlarmItems sharing properties (ack rules, sounds, auto-ack).
AlarmItem
A tag monitored by the Alarm module (condition/limits/deadband/message).
Application / Project / Solution
All terms can be applied generally to automation implementations. Specifically in the FrameworX technical documentation:
- Project refers to FactoryStudio project files
- Solution is FrameworX Implementation
- Application is the end use of that configuration
Application Modules
Pillar 3 modules that implement business logic and data processing: Datasets, Reports, Scripts. Functional name: Business Operations.
Asset Tree
Hierarchical model of equipment/templates (recipes, setpoints, status, etc.).
When used in one word, AssetTree, refers specifically to the FrameworX UNS AssetTree.
AssetFolder
Folder node in the AssetTree, addressed at runtime as Asset("/path"). The structural element grouping tags by physical or logical hierarchy.
Audit Trail
Runtime log of configuration changes and key events for diagnostics/compliance.
Build / Publish
Build compiles the solution. Publish creates a read-only, deployment-ready package for validated environments.
Built-in Namespaces
The 12 runtime namespace roots the platform exposes automatically — Tag (the UNS) plus Alarm, Device, Historian, Dataset, Script, Report, Display, Layout, Security, Server, Client, and Info. Every configured object becomes a live .NET object under one of these roots, accessible via dot notation in scripts, expressions, and display bindings. See Built-in Namespaces Reference.
Business Operations
Functional name for Pillar 3 of the Four Pillars Methodology. Modules: Datasets, Reports, Scripts. Equivalent organizational name: Application Modules.
Categories
Lightweight labels to organize large configurations across tables.
Channel (Devices)
Protocol endpoint configuration (driver type, serial/TCP settings, timeouts, etc.).
Client (runtime client)
A connected runtime session (desktop or browser). Includes .NET (desktop) and WebAssembly clients. Engineering sessions are not clients.
Client Domain / Server Domain (value scope)
Scope of object values at runtime: server-wide vs. client-local.
CodeBehind
Custom C# or VB.NET code for Displays event handling/logic; may call Python classes.
Component (User Control)
Reusable UI element used in Displays (buttons, charts, inputs, custom).
Data Connection
Link to external systems (PLCs, databases, OPC UA, MQTT, etc.).
Data Foundation
Functional name for Pillar 1 of the Four Pillars Methodology. Contains the Unified Namespace: Tags, AssetTree, UserTypes, Enumerations, and TagProvider Services.
DataHub Station
Distributed server extending Enterprise for field-level processing (I/O, Alarms & Historian).
DatasetDB
External database connection defined in the Datasets module.
DatasetFile
Logical file interface for reading/writing ASCII/Unicode/XML from Datasets.
DatasetQuery
Configured SQL query with parameters and execution methods.
DatasetTable
Mapping of tags to DB columns for read/write.
DataTemplate (legacy)
Legacy term — see UserType.
Designer (Solution Designer)
Configuration environment for all modules (Displays, Tags, Devices, Alarms, Historian, etc.).
Display (Screen)
Visual container for UI built in the Designer.
Displays Portal
Distributed server extending Enterprise for operator UI and user management.
Direct Binding (no local tags, no-mapping required)
Bind UI/logic directly to external namespaces (MQTT/Sparkplug topics, OPC UA node IDs) without first mirroring tags locally. Great for prototyping/diagnostics; for production, promote bindings into the UNS/tag model. Implemented by the Dynamic TagProvider technology.
Domain (runtime domain)
General term for Server/Client domain value scope.
Dynamics (Animations)
Visual changes in UI elements driven by tag values (color, size, visibility, etc.).
EdgeConnect
Industrial Edge Computing Platform, including Edge SQL (access to local & remote SQL Databases) and other features powered by Tatsoft FrameworX Platform.
Edge SQL
(In EdgeConnect) Read/write local SQL at the edge and access remote SQL servers from the edge node.
Enumerations
State maps for discrete values (labels, colors, bit states).
Example
A short code snippet showing a concept; may link to a Sample for a full app.
Execution Profile
Named runtime configuration that selects which modules start, the runtime port, and the database/storage bindings. Four built-in profiles: Production (port 3101), Development (3201), Validation (3301), Custom (3401). The same .dbsln solution can run concurrently under different profiles for lab / FAT / SAT separation. See Runtime Execution Profiles Reference.
FactoryStudio
Tatsoft's 2012–2024 product that evolved into FrameworX. A guided, fully compatible upgrade path to FrameworX 10.1 is provided.
Four Pillars
The Designer's organizational methodology for building solutions in dependency order: Data Foundation → Industrial Operations → Business Operations → User Interactions (also called Unified Namespace → Process Modules → Application Modules → Operator UI Modules). Each pillar builds on the previous; configuration follows pillar order. See Four Pillars Methodology.
FrameworX (platform)
Tatsoft's core runtime + designer platform for SCADA/IIoT/UNS. All modules included. One designer for .NET (desktop) & WebAssembly.
FrameworX AI Chat
Chat-for-Displays feature exposed as a first-class Display action type, peer to SQL Query, REST API, and Server Class. A Display configures a ChatRequest action that, when invoked at runtime, sends a chat request to Local AI and returns the response for display or follow-on logic. First feature delivered on the Local AI capability. See Local AI.
FrameworX Enterprise Unlimited
Edition with unlimited I/O and clients (Server or Site scope). Same features as Enterprise I/O tiers; scope differs.
FX MQTT Broker (built-in broker)
Built-in MQTT broker with Sparkplug B support (also exposes a client).
FX MQTT Simulator
Tool to simulate MQTT clients and Sparkplug payloads for testing.
Graphical Element
Primitive or composite UI element (shape, icon, chart, gauge, control).
HistorianTable
Storage policy configuration for tag history (retention, compression).
HistorianTag
A tag enrolled into one or more HistorianTables.
Hot Reload (Hot reloads)
Apply certain offline configuration changes to a running system without a full restart.
Hot-Standby (HA)
Primary/standby server redundancy for systems requiring High-Availability.
Image Resources / Industrial Icons
Graphic assets available to Displays, including industry-specific symbol sets.
Industrial Operations
Functional name for Pillar 2 of the Four Pillars Methodology. Modules: Devices, Alarms, Historian. Equivalent organizational name: Process Modules.
Internal Module
Background service exposed by the platform that requires no user configuration.
Layout
Display arrangement pattern (canvas vs grid; responsive breakpoints). Also a runtime namespace root (Layout.*) — display layout objects accessible from scripts and bindings.
Local AI
AI capability that runs locally inside the FrameworX runtime, with no cloud dependency — customer data stays in the plant. The industrial differentiator: on-prem execution, no per-call cost, no data egress, and operation in air-gapped deployments. Powered by a bundled or customer-provided LLM that integrates with FrameworX features. First consuming feature: FrameworX AI Chat.
MachineHMI
FrameworX product for panel/embedded HMI applications. See Product Editions for details.
MCP (Model Context Protocol) Tools
AI-facing tool surfaces the platform exposes for Designer authoring, runtime data access, and solution automation. Solutions can publish their own MCP Tool classes via Scripts → Classes. See AI + Runtime Connector and Designer MCP references.
Modifier (Device/Points)
Per-point addressing options (arrays, bits, string formatters).
Modular Architecture
Separation of platform capabilities into interoperable modules.
Module
Executable unit (e.g., Alarms, Devices, Historian) connected to the runtime database.
Namespace
Qualified path space for runtime objects. The platform exposes 12 built-in namespace roots — Tag.* (the UNS) plus 11 module/system roots that together form the runtime Object Model. See Built-in Namespaces.
Node (Devices)
A device instance under a Channel (identifies the physical equipment).
Object Model
The full runtime object hierarchy of a solution — 12 namespace roots (the UNS plus eleven built-in module and system namespaces) exposing every configured tag, alarm, device, display, etc. as a live .NET object. Broader than the UNS: the UNS is Pillar 1 (Tag.* only); the Object Model includes UNS plus all built-in namespaces. See Object Model Quick Reference and Built-in Namespaces.
Object Type (RunObj type)
Runtime object category (Display, Report, Script, etc.).
ObjectValues / PropertyValue
Runtime properties on tags/objects (read/write at runtime).
Online Configuration
Edit/apply changes while the system is running (with safety rules).
Operator UI Modules
Organizational name for Pillar 4 — modules that present information and accept operator input: Security, Displays, Clients. Functional name: User Interactions.
PanelType
Display layout mode: Canvas or Grid.
Parameters (Tag Configuration)
Settings that define tag behavior (scaling, deadband, engineering units, etc.).
Permissions / PermissionGroup
Role-based access control for design and runtime operations.
Pillar
One of the four organizational levels in the Four Pillars Methodology. See Four Pillars.
Plugin
Reusable packaged component pieces (UI, logic) importable into a solution. (Distinct from third-party AI-tool plugins such as Claude Code plugins — those are unrelated.)
Policies (login/session)
Rules for authentication, lock, timeout, and session handling.
Point / DevicePoint
Addressed value from a device/register mapped into the runtime database (via Devices: Channels/Nodes/Points).
Process Module
Pillar 2 modules that interact with the physical process: Devices, Alarms, Historian. Functional name: Industrial Operations.
Process Tag
Tag reflecting real-world signals (via device/OPC/MQTT mapping or calculations).
Product Series / Editions
FrameworX products and their editions (Enterprise Unlimited; Enterprise 1,500/5,000/15,000; MachineHMI 150/500/1,000; EdgeConnect).
Project File (legacy)
FactoryStudio file formats (.tproj, .trun). Replaced by v10 Solution .dbsln files.
Protocol
Supported communication rule set (driver): e.g., Modbus, EtherNet/IP, OPC UA, MQTT/Sparkplug.
Property / Attribute
Named field on a runtime object (e.g., Display.Title, Tag.EngineeringUnits).
PropertyWatch
Live inspector for viewing/editing object/tag properties during runtime.
Real-Time Database (Runtime DB, RtDB)
In-memory database backing runtime tags/objects.
Rendering Engine
Graphics runtime layers that render Displays on .NET (desktop) and WebAssembly.
Report / Report Form
Rich-formatted output with embedded real-time data; exportable (PDF/JSON/XML/CSV/Text).
Reports WebData / WebData
Interfaces for JSON/XML/HTML data exchange and file output.
Runtime
Phase where the solution executes, connects to devices, renders UI, and serves clients.
Runtime Database
See Real-Time Database (RtDB).
Runtime Startup
Runtime initialization via the platform host (e.g., TStartup.exe/TServer.exe) and service configuration.
RuntimeUser
Authenticated user identity for runtime access.
Sample Solution
A runnable project you can download/clone to reach first value fast.
Script Reference
External assemblies referenced by scripts/displays.
ScriptClass
Reusable C#/VB.NET/Python class used by scripts and displays.
ScriptExpression
Single-line expression for lightweight actions.
ScriptTask
Script unit triggered by events/timers.
Smart Symbol
Reusable, parameterized UI component bound to data/templates.
Solution
A complete configuration (tags, devices, displays, logic, alarms, storage).
Solution File / Solution Name
The saved configuration artifact (.dbsln) and its canonical name.
SolutionDB / Solution Database
Database file storing configuration for a solution.
Source-Linked Tags (UNS)
UNS tags whose Source link points to an external path (MQTT/Sparkplug topic, OPC UA node). The Dynamic Tag Provider auto-manages runtime communications on demand. Keeps local names, intellisense, cross-refs, and offline fields (Quality/Min/Max) without Device configuration.
Source link (field)
Per-tag link to a provider + address (e.g., MQTT topic, OPC UA node). At runtime, communications are created/maintained as displays/scripts need data, respecting protocol constraints.
Sparkplug B
MQTT specification for stateful, interoperable industrial payloads.
StorageLocation
Configured target for historian data (local/remote storage).
Tag
Named variable for real-time/historical data with type, quality, timestamp.
Tag Type
Data kind (Integer, Float, Boolean, Text, etc.).
TagProvider Service (TagProvider API)
Programmable service that resolves Direct Binding paths at runtime (MQTT topics/OPC UA nodes) and manages protocol-safe communication groups. Powers Source-Linked Tags, locally defined at the UNS; and connection to Historian Storage Locations from external systems.
Target Platform
Runtime host target (Windows .NET desktop; WebAssembly for browser/mobile; Edge runtimes; where applicable .NET 10/Linux).
Task (Script.Task)
Program unit in C#, VB.NET, or Python executed by the script engine.
Time-Series
Timestamped values recorded over time (stored in the Tag Historian).
Trust (Full/Partial)
Runtime permission level controlling access to OS resources.
Unified Namespace (UNS)
The platform's data foundation (Pillar 1). Strictly comprises Tags, UserTypes, Enumerations, AssetTree, and TagProvider Services. UNS is one root of the broader runtime Object Model; the eleven other module and system namespaces (Alarm, Device, Historian, Dataset, Script, Report, Display, Layout, Security, Server, Client, Info) are peers of UNS, not sub-regions of it.
User
Any authenticated person using the designer or runtime clients.
User Interactions
Functional name for Pillar 4 of the Four Pillars Methodology. Modules: Security, Displays, Clients. Equivalent organizational name: Operator UI Modules.
UserType (UDT, DataTemplate)
User-defined data structure composed of typed members; supports nesting and inheritance from a base UserType. Used to instantiate structured tags in the UNS. (Legacy term: DataTemplate.)
Visibility (Tag Visibility)
External visibility flags for tags (Public/Protected/Private).