Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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).


Animations

Visual changes in UI elements driven by tag values (color, size, visibility, etc.).


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 Domain (.NET AppDomain)

Isolated runtime boundary for managed code.


Application Modules

Modules that Implement the business logic (Datasets, Reports, Scripts).


Assembly

Managed .NET binary (.dll/.exe) produced by build.


Asset Tree

Hierarchical model of equipment/templates (recipes, setpoints, status, etc.).
When used in one word, AssetTree, refers specifically to the FrameworX UNS AssetTree.


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.


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.).


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 (UDT)

User-defined data type, data structure; supports nesting and template references.


Designer (Solution Designer)

Configuration environment for all modules (Displays, Tags, Devices, Alarms, Historian, etc.).


Display (Screen)

Visual container for UI built in the Designer.


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.


DLL Hell

Legacy issue from shared DLL conflicts when using unmanned code and direct OS calls; mitigated by .NET assembly isolation.


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.


FactoryStudio

Tatsoft’s 2012–2024 product that evolved into FrameworX. A guided, fully compatible upgrade path to FrameworX 10.1 is provided.


FrameworX (platform)

Tatsoft’s core runtime + designer platform for SCADA/IIoT/UNS. All modules included. One designer for .NET (desktop) & WebAssembly.


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 Updates)

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.


Internal Module

Background service exposed by the platform that requires no user configuration.


Layout

Display arrangement pattern (canvas vs grid; responsive breakpoints).


MachineHMI

FrameworX edition for panel/embedded HMI. 


MCP Server

Built-in API surface to build solution-specific tools/automations (e.g., generate tag trees, UNS operations). Also used as an orchestration hook for external analytics/AI.


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 and external sources.


Node (Devices)

A device instance under a Channel (identifies the physical equipment).


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).


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.


Plugin

Reusable packaged component pieces (UI, logic) importable into a solution.


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

Modules that interact with the physical process (Alarms, Devices, Historian).


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 150/500/1,500; MachineHMI 150/500; 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 (alias: DataSource, deprecated name) 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. Alias: DataSource (deprecated label in UI; use “Source link”).


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. It allows 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 8/Linux).


Task (Script.Task)

Program unit in C#, http://VB.NET , or Python executed by the script engine.


Time-Series

Timestamped values recorded over time (stored in the Tag Historian).


Toggle

Binary change action (0/1).


Trust (Full/Partial)

Runtime permission level controlling access to OS resources.


Unified Namespace (UNS)

Shared, structured data model for organizing/publishing/consuming system data across operations.


User

Any authenticated person using the designer or runtime clients.


Visibility (Tag Visibility)

External visibility flags for tags (Public/Protected/Private).


...



Notes on changes (for editors)

Add:

  • Sparkplug B — MQTT payload spec used by FrameworX UNS; supported across platform components. (Style: “Sparkplug B”.) 

  • UNS (Unified Namespace) — Brokered namespace for plant/enterprise data; FrameworX provides native broker+client and tooling to promote/bind tags. 

  • Direct Binding — Bind UI/logic directly to external sources without creating local tags.

  • Source-Linked Tag — Local tag that keeps governance/naming while linking its value to an external source (on-demand comms). 

  • Data APIs — Programmatic endpoints (incl. REST/HTTP, MCP Server) for data/service access; excluded from MachineHMI. 

  • Edge SQL — Dataset engine capability to read/write SQL at the edge (local & remote). 

  • WebAssembly (WASM) client — Browser runtime for Displays; same designer targets .NET desktop and WebAssembly. 

  • I/O (licensing) — One unique externally sourced variable bound into the solution (counts once regardless of reuse; internal variables don’t count). (Point to this entry from any place that mentions scaled editions.)   

  • EdgeConnect— Standalone Edge UNS/IIoT Platform

  • DataHubNode — additional node on Enterprise Unlimited deployments, add distributed processing capabilities for Devices(I/O), Alarms, Historian & Script.
  • ApplicationNode - additional node on Enterprise Unlimited deployments, add independent Displays Portal, for local governance of displays and users.


  • Runtime phrasing standardized to “.NET desktop & WebAssembly (web/mobile)” (no “WPF” in public terms).

  • FrameworX Unlimited clarified as an edition (unlimited I/O & clients), not a licensing model.

  • Duplicates merged (Runtime DB/RtDB).

  • FactoryStudio marked historical with guided upgrade path to v10.1.




If you want this split into two views (Public vs. Developer) with a filter or icon tag in Confluence, I can provide labels for each entry so it renders cleanly in both contexts.