Introduction
Every knowledge area domain has its own terminology, and software applications are no exception. While the nomenclature used on this platform follows market standards our platform uses industry-standard terms whenever possible, some specific terms may have special certain words may carry specific meanings in this context.
We recommend reviewing this glossary after you've gained some experience with the platform. Revisiting these definitions will help clarify key concepts and improve your efficiency when building applications.
Jump to: A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Glossary (A-Z)
Anchor letter-a letter-a
This glossary includes the key terms and concepts used by our platform, as well as relevant technologies.
It is recommended to read this glossary at least once after using our platform for a few months. Reviewing the definitions and concepts, combined with your experience, will enhance your understanding of the system and improve your efficiency in creating applications.
Name
AccessTypes, Device AccessType
Each
DevicePoint is
associated withassigned an AccessType,
defining rules for when to read and/or write values. It includes settings likewhich defines its read/write behavior, including polling rate and
read/writepermissions
, allowing users to configure the data acquisition and the sending of commands to the devices with total flexibility.
AlarmArea
A hierarchical grouping of AlarmGroups for structured alarm management.
Can contain child AlarmAreas, useful for large systems
with many AlarmItems configured.
AlarmGroup
A collection of AlarmItems sharing common properties. Simplifies configuration with settings like AckRequired, AutoAckTime, and Sound.
AlarmItem
A tag or expression monitored by the Alarm Module,
including condition, limit, deadband, and message settings.
AlarmGroup
A collection of AlarmItems sharing common properties. It simplifies alarm management with configuration properties like AckRequired, AutoAckTime, and Sound.
App Domain, Application Domain
A virtual, isolated environment
for running a .NET application
runs. This isolation provides safety, preventing one process from interfering with another, providing process isolation.
Application, Project, Solution
"Project" applies to version 9.2
or older versions, while “Solution” is for version 10 and upand earlier. "Solution" applies to version 10+. "Application"
is used to refer to the functionally the configuration is intended to perform, in opposition to "Project" and "Solution" that are more closely related to the configuration itselfrefers to the functional use of the configuration.
Application Modules
Modules that
manage andexecute a system's internal logic and
datatransformations
. They encompass Scripts,
Reports, and Datasets. Manage and execute a system’s internal logic and data transformations,including
the Modules:Datasets, Reports, Scripts, and Displays.
Assembly
An executable file (.EXE or .DLL) created using managed code
within the .NET framework.
Asset Tree
A hierarchical
view of
the solution data, containingvariables
, Tags, and DataTemplates matching sensor reading physical equipments, setpoints, recipes, management data, and all the variables necessary to implement and operate an applicationand templates reflecting equipment, recipes, setpoints, and other process data.
Audit Trail
Logs changes and events
during runtime execution, useful for diagnostics and compliance.
Build and Publish Anchor letter-b letter-b
Build
processcompiles the solution
code, while; Publish creates a read-only version for
distributiondeployment in
regulated sitesvalidated environments.
Categories Anchor letter-c letter-c
Labels used
across configuration tablesto organize large
solutionsconfigurations across multiple tables.
Channels
Configuration object in the Devices Module
specifying communication protocol and settings.
Client
Software interacting with
athe server or
services, includingruntime. Includes .NET
Clients, HTML5
Clients, and Remote Clients.
Regarding Scripts or Tags, refers to the Client Domain, meaning values that reside and methods that are executed on the client software components.CodeBehind
In scripting, "Client Domain" refers to client-local values.
Client Connection
A runtime connection to the solution from a local or remote station. Does not include engineering sessions.
CodeBehind
Custom
VB.NET or C# code used for event handling, calculations, and
applicationbehavior
management.
ItCan also
allows tocall Python classes.
Component, User Controls
Graphical controls used in displays. Includes buttons, inputs, and custom elements.
Connection Target
Defines the
location of thedata source
, selecting from(Local Solution,
TagProvidersTagProvider, or Remote
sources.source).
Data Connections Anchor letter-d letter-d
Links between the platform and external systems (PLCs, databases, OPC, MQTT, etc.) for I/O.
DatasetDBs
Settings in the Datasets Module for external database connections.
DatasetFile
A logical object in the Datasets Module for reading/writing
Component, User Controls
Graphical User Controls available for creating displays, including customizable objects and elements.
DatasetDBs
Connection settings created by the Datasets Module to communicate with an external database.
DataTemplate (UDT)
User-defined data structures that include variables and references to other templates, creating a hierarchical data structure.
DatasetFile
ASCII, Unicode, or XML
formatsfiles.
DatasetTable
DatasetQuery
A configured SQL query in the Datasets Module
DatasetQuery
, with properties and methods for execution.
DatasetTable
A table mapping Tags to database columns for read/write operations.
DataTemplate (UDT)
User-defined data structure with nested variables and template references.
Designer, Solution Designer
The
interface used to configure FrameworX solutions.
Display / Screen
A window or frame of your application’s user interface, containing static or dynamic graphical elements.
Draw
Part of the Solution Designer used to draw and animate displays and synoptic screens.
DLL Hell
Visual container for user interface elements.
DLL Hell
Conflicts from shared DLLs in legacy systems, addressed by .NET’s assembly isolation.
Domain, Server Domain, Client Domain
Object value scope during runtime: Server-wide vs. Client-local.
Draw
Designer module for building synoptic screens and animations.
Dynamics and Animations
Definition for changes in the graphical elements attributes, driven by the values of real-time tags.
TagProvider Connections
Enable direct interaction with variables, tags and data structures in remote systems without creating specific tags, enhancing data access within the Unified Namespace.
Enumerations
Define potential values or ranges for a variable, mapping messages and colors to each state.
Forms, Report Forms
Rich Text documents that can include real-time tag values, tables, and symbols, saved as Text or PDF files.
Graphical Element
Components used in screens, such as shapes, checkboxes, or trend charts.
Image resources
Imported image files used as graphical elements in your solution.
Industrial icons
Pre-built icons designed for industrial automation applications.
Internal Module
Features and programs that implement internal system functions, running without user configuration.
FactoryStudio
A scalable product version for SCADA/HMI, IIoT Edge, and Gateway applications, built on Tatsoft’s FrameworX.
FrameworX
The software platform and underlying technologies and components.
FrameworX Unlimited
Changes to graphical attributes based on tag values.
EdgeConnect Anchor letter-e letter-e
Product series designed for IIoT and embedded edge devices.
Enumerations
Maps possible tag values to states, labels, and colors.
FactoryStudio Anchor letter-f letter-f
A scalable version of FrameworX for SCADA/HMI and IIoT Edge applications.
Form, Report Form
Rich text document that can embed real-time data and symbols; exportable to PDF.
FrameworX
The core software platform and runtime environment.
FrameworX Unlimited
Licensing model with unlimited Clients, Developers, and Connections.
FX EDGE
A FrameworX
deployment for edge computing scenarios.
FX MQTT Broker
Built-in MQTT broker in the FrameworX
Platformplatform.
FX MQTT Simulator
An MQTT Client simulator with Sparkplug, included in the product installation.
Simulator for testing MQTT Clients and Sparkplug payloads.
Graphical Element Anchor letter-g letter-g
Basic UI elements like shapes, charts, and controls.
HistorianTables Anchor letter-h letter-h
Group tags for historical logging with storage and retention policies.
HistorianTag
Tag configured for storage in a HistorianTable, optionally referencing external sources.
Hot Updates (Hot Reload)
Apply offline changes to the runtime without restarting execution.
Image Resources Anchor letter-i letter-i
Graphics imported into the application as visual assets.
Industrial Icons
Pre-built graphics suited for industrial applications.
Internal Module
Background functionality that operates without user configuration.
Anchor letter-j letter-j Anchor letter-k letter-k
Layout Anchor letter-l letter-l
Arranges UI into panels or grids. Supports Canvas and Dashboard styles.
MachineHMI Anchor letter-m letter-m
Product series for OEM and factory-floor operator panels
Hot Updates (Hot Reload)
Apply offline solution changes without disrupting the runtime environment, maintaining stability and preventing downtime.
HistorianTables
Groups Tags for historical archiving, defining settings for storage and retention.
HistorianTag
Tags whose values are stored in a HistorianTable, including dynamic references to external data.
Project File
SQL Studio encoded database containing the Project configuration, with extensions .TPROJ and .TRUN.
Layout
.
Modifier (Device/Points)
Parameter for DevicePoints enabling custom access for arrays, bits, and strings.
Modular
architectureBreaks down complex functionalities into distinct modules, providing flexibility in design and configurationArchitecture
System design that splits functionality into interchangeable modules.
Module
Executable unit interfacing with the real-time database
, composed of one or more Assemblies.
Namespace
An address space with unique names for objects, grouping process variables, modules properties and methods, etc.
Logical space where named runtime objects exist.
Nodes Anchor letter-n letter-n
Objects in the Devices Module specifying connection to physical equipment.
Anchor letter-o letter-o
Nodes
Device Module object defining the settings to physical devices, using the protocol defined in the DeviceChannel. Each Node contains one or more DevicePoints.
Online Configuration
Object Type (RunObj type)
Identifies the type of runtime object (
display, report, scripte.g., Display, Report, Script).
Objects, Runtime Objects
Visible objects in the Solution, accessed via scripts and displays, updated by the respective execution modules.
PanelType
Defines how graphical elements are organized, supporting Canvas and Dashboard types.
Canvas (or Process Screens): The elements are in a drawing surface, where each element has its specific location and size.
Grid (or Dashboard Screens): The elements are placed in a grid with responsive size, columns and rows. The graphical elements adjust accordinglyEntities managed and accessed in runtime via displays and scripts.
ObjectValues, PropertyValue
Runtime properties of Tags and system objects.
Online Configuration
Ability to edit running systems in real time.
PanelType Anchor letter-p letter-p
Defines layout style (Canvas or Grid) for UI elements.
Parameters (Tag Configuration)
Settings that define tag behavior and data handling.
Permissions, PermissionsGroup
Set levels of access for users, determining their capabilities within the solution.
Policies
Access levels and user role definitions.
Plugin
Subset of a FrameworX Solution, exported and imported using the Solution-Export command. Reusable components of a solution, containing Tags, Displays, or other objects.
Reusable component exported/imported from a solution.
Policies
Rules for login and user session handling.
Points, DevicePoint
Mapped values representing physical I/O or register addresses.
Process Modules
Modules such as
ObjectValues, PropertyValue
Properties defined for runtime objects, such as Tags and DeviceNodes.
PropertyWatch
Diagnostic utility to check and modify object values at runtime.
Parameters (Tag Configuration)
Defines behavior and value processing for Tags.
Process Modules
Alarms, Devices, and Historian that interface with the physical process.
Points, DevicePoint
Individual items read or written from/to DeviceNodes, mapping specific Tags to device registers or PLC I/O addresses.
Product Family
Process Tag
Tag that reflects real-world data via devices or other sources.
Product Family
Platform variants: FrameworX, FactoryStudio,
MachineHMI,
and EdgeGatewayEdgeConnect.
Product Family and Model
Defines runtime licensing requirements
for running the Solution in production.
Project File
In
versions before v10, contains project configuration (.tproj, .trun).
Protocols
Communication rules supported by the Devices Module.
Property or Attribute
Defined value of a runtime object.
PropertyWatch
Tool for live inspection/modification of values.
Anchor letter-q letter-q
Real-Time Database Anchor letter-r letter-r
Protocols
Rules for communication between devices, supported by the software.
Solution
Application for real-time data built on the platform, including configurations for all Modules.
SolutionDB / SolutionDatabase
Database containing configuration information, with extension .dbsln.
Solution File / Solution Name
Configuration of an application saved in a .dbsln file, matching the solution name.
Property or Attribute
Associated value of a Tag or object.
, RunDB, Runtime Database, RtDB
In-memory database
that stores tag data during
solutionexecution
, implemented by the TServer.exe process.
Rendering Engine
Graphics rendering engine supporting WPF, HTML5, and Portable Clients.
Reports WebData
Interfaces for JSON,
XML, HTML data exchange or file output.
Runtime
Phase where
the solution
is in active execution, utilizing configured modules for tasks, data management, and operationsexecutes in real time.
Runtime Database
The core in-memory
real-time database for Unified Namespace data, ensuring efficient data management during solution execution.RuntimeUsers
Users created and retrieved from an external encrypted SQL database or other identification servers.
TargetPlatform
database used during solution execution.
Runtime Startup
The initialization of the
Solution atruntime,
performedhandled by TStartup.exe or TServer.exe.
RuntimeUsers
Authenticated users stored in secure databases or identity providers.
Script References Anchor letter-s letter-s
DLLs referenced by scripts and displays.
ScriptClass
Reusable code library for use in script and display logic.
ScriptExpression
Single-line
of code responding to an eventcode for simple runtime actions.
ScriptTask
Script block triggered by events or timers.
Smart
symbolsGraphical elements with dynamic properties and connections to real-time tags and templates.
Symbols
Reusable graphical components bound to data and templates.
Solution
A complete application configuration built using the platform.
Solution File / Solution Name
Saved configuration file (.dbsln) with the solution's name.
SolutionDB / SolutionDatabase
Database file storing the configuration of a solution.
StorageLocation
Defines where historian
data is saved or retrieved.
Tag Anchor letter-t letter-t
A named variable representing real-time
andor historical data
, created locally or accessed remotely.
Tag Type
Specifies the kind of data (e.g., Integer, Digital, Text).
TagProvider Connections
Enable live access to external data sources without redundant tags.
TargetPlatform
Specifies runtime host platform (Windows/.NET Framework or .NET 8/Linux).
Task (Script.Task)
A code program written in C#, VB.NET, or Python
running during solution runtime.
Time-Series
Time-Series data is a collection of data points, often recorded sequentially over time. Each entry typically includes a data value and a timestamp (e.g., temperature reading at a specific time). Using UTC time helps align data from various time zones.
Sequentially recorded data points with timestamps.
Toggle
Switches a value between 0 and 1
Toggle
.
Trust, Partial Trust, Full Trust
Execution permissions: full vs limited system access.
Anchor letter-u letter-u
Unified Namespace
A
shared data model for organizing, publishing, and consuming system data.
User
Any individual accessing the application via design or runtime interfaces.
Anchor letter-v letter-v
Users
Anyone accessing the solution, either through the Designer Tool or in runtime mode (Displays).
Visibility (Tag Visibility)
Defines
•Protected: Read-only access.
•Private: Not accessible by external applications and may have different values on each client machine.
WebData, Reports WebData
external visibility for tags: Public, Protected, or Private.
Anchor letter-w letter-w Anchor letter-x letter-x Anchor letter-y letter-y
WebData Anchor letter-z letter-z
Supports data exchange formats and interactions with REST APIs.
In this section:
Page Tree | ||||
---|---|---|---|---|
|