Page History

Complete reference of all FrameworX objects: what you can create, dependencies, and minimum configuration.

Reference → Platform Modules Reference → Object Model Quick Reference

Architecture Concepts

The Triple Mirror Pattern

The FrameworX object model follows a one-to-three mirror system where the same structure reflects across:

Learning one structure teaches you all three.

Three-Level Hierarchy

All configurable objects follow a consistent hierarchy:

• Module Container (or RunDBRoot)
  • Collection Table (plural naming, e.g., AlarmsGroups)
    • Object Instance (singular naming, e.g., AlarmGroup)

Naming Conventions

Designer ↔ Object ↔ Database: One-to-one mapping across Designer UI pages, object model classes, and SQLite tables in the solution file (.dbSLN).

Named Objects vs Configuration Rows

Named Objects have unique names within their namespace and appear in the Designer navigation tree where users can create new instances. Internally, named objects are stored as tokens for efficient referencing — the Designer UI displays friendly names, but solution files store tokenized references.

Configuration Rows are objects without unique name identifiers, configured in grid/table editors:

Quick Navigation

UNS (Data Foundation)

The Unified Namespace holds all process variables and provides the central data layer for all modules.

Objects

Pre-defined Objects

None — user creates all objects.

Tag — Minimum Configuration

Tag Path and Access

UserType vs Tag

UserTypes and Tags have nearly identical structure:

• Tag has PATH column (instance in hierarchy)
• UserType has no PATH (template for creating Tags)

When a Tag uses a UserType, members are accessed as: Tag.Motor1.Speed, Tag.Motor1.Status

TagProvider Services

Enable dynamic external data without pre-defining tags:

1. Create TagProvider Service with connection credentials
2. Attach to a node in the Asset Tree
3. Children are queried directly from external source
4. Access via Asset("path") syntax only

→ Unified Namespace Reference

Devices (Industrial Operations)

Connects to field devices and maps device data to Tags.

Objects

*Protocol is built-in, query only

Pre-defined Objects

Hierarchy

Protocol (built-in, select only)

Channel (protocol 

• +

• settings)

• • Node (channel

• • +

• • device

• • address)

• • • Point (tag + address)

Dependencies

Point — Minimum Configuration

→ Devices Module Reference

Alarms (Industrial Operations)

Monitors Tags for alarm conditions and manages alarm events.

Objects

Pre-defined Objects

Dependencies

AlarmsItem — Minimum Configuration

→ Alarms Module Reference

Historian (Industrial Operations)

Records Tag values over time for historical analysis.

Objects

Pre-defined Objects

Hierarchy

Hierarchy

• StorageLocation

• (database

• connection)

• • HistorianTable (storage

• • rules)

• • • HistorianTag (which

• • • tags)

Dependencies

HistorianTag — Minimum Configuration

→ Historian Module Reference

Datasets (Business)

Connects to SQL databases for queries, table operations, and file I/O.

Objects

Pre-defined Objects

Dependencies

DatasetQuery — Minimum Configuration

→ Datasets Module Reference

Reports (Business)

Generates documents and handles web data interchange.

Objects

Pre-defined Objects

None.

Dependencies

→ Reports Module Reference

Scripts (Business)

Custom code execution in C#, VB.NET, or Python.

Objects

Pre-defined Objects

None.

Dependencies

ScriptExpression Note

ScriptExpressions can auto-trigger when referenced Tags change value.

→ Scripts Module Reference

Security (UI)

Users, permissions, and access control.

Objects

Pre-defined Objects

Dependencies

SecuritySecret

Encrypted storage for passwords used in Datasets (DB connections) and Devices (device connections).

→ Security Module Reference

Displays (UI)

Operator interface screens and layouts.

Objects

Pre-defined Objects

Dependencies

Display Types

→ Displays Module Reference

→ Display Controls Reference

Configuration Dialogs

These are built-in settings dialogs to the solution or specific modules, not

objects

to be created. 

Solution Categories

Solution categories are metadata information labels, created by the user, that be can applied to any object in the system. 

All Objects Summary

Runtime Namespace Reference

Syntax by Context

Domain Separation

Even on a single computer, separate processes maintain this separation for security and performance.

→ Built-in Namespaces

→ Built-in Namespaces Reference

Objects with Custom Editors

The following objects have dedicated visual editors. Content is stored in hidden *Contents tables managed internally by the system:

Tag Types Reference

Built-in Types

UserType References

UserTypes are assigned IDs starting at 201:

• First UserType created: ID 201
• Second UserType: ID 202
• And so on...

In JSON, reference a UserType with: "Type": 201

See Also

• Built-in Namespaces — Conceptual overview
• Built-in Namespaces Reference — Detailed namespace documentation
• Namespace API Reference — Complete API documentation
• Git Integration and Export Reference — Version control and JSON export
• JSON Import Export Specification — Detailed JSON field reference (new page)