The Designer 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 methodology that structures data flow from field connectivity to user visualization.

Key Capabilities:

  • Configure all modules in one workspace
  • Test solutions without deployment
  • Support multi-user collaboration
  • Provide IntelliSense and validation
  • Enable offline and online editing



Key Concepts

ConceptDescriptionImpact
Unified WorkspaceSingle environment for all configurationNo need to switch between tools
Object Model.NET-based classes with inherited propertiesAccess methods without custom code
IntelliSenseContext-aware auto-completion everywhereFaster, error-free configuration
Test ModeIn-Designer runtime executionValidate without deployment
Modular ArchitectureIsolated module changesChanges won't break other modules
Multi-User SupportConcurrent engineering capabilityTeam collaboration on same solution




In this section...


What Designer Does

ConfigurationDevelopment ToolsTesting & Validation

Define tags and data models

Configure field devices

Setup alarms and historian

Create scripts and logic

Design displays and UI

Manage security settings

IntelliSense everywhere

Real-time validation

Cross-reference tracking

Refactoring support

Import/export capabilities

Version control

Execution Profiles

Online configuration

Simulation tools

Error checking

Performance monitoring

Build validation


Workspace Layout

???????????????????????????????????????????????????????????????
?  Menu Bar            [File][Edit][View][Tools][Help]        ?
???????????????????????????????????????????????????????????????
?              ?                        ?                     ?
?  Navigation  ?     Design Canvas      ?   Properties        ?
?     Tree     ?                        ?     Panel           ?
?              ?   (Context-Sensitive)  ?                     ?
? ? Solution   ?                        ?  Tag: Temperature   ?
?   ? UNS      ?                        ?  Type: Float        ?
?     • Tags   ?                        ?  Min: 0             ?
?   ? Devices  ?                        ?  Max: 100           ?
?   ? Displays ?                        ?  Units: °C          ?
???????????????????????????????????????????????????????????????
?  Output Window      [Build][Errors][Cross-Reference]        ?
???????????????????????????????????????????????????????????????


Solution Development Workflow

Following the Four Pillars methodology, Designer guides you through a structured configuration process:

PhasePillarConfiguration TasksDesigner Areas
1. FoundationP1: UNS• Create tags
• Define UserTypes
• Build Asset Tree		UNS → Tags, Templates, Assets
2. IntegrationP2: Process• Setup devices
• Configure alarms
• Enable historian		Devices, Alarms, Historian
3. LogicP3: Application• Create scripts
• Setup datasets
• Build reports		Scripts, Datasets, Reports
4. VisualizationP4: Operator UI• Design displays
• Create symbols
• Configure clients		Displays, Symbols, Layouts



Module Organization by Four Pillars

Pillar 1: UNS Foundation - Define Your Data

Pillar 2: Process Modules

Unified Namespace (Local UNS) - Tags & UDTs

Devices, Field Connections: 100+ connectors

DataExplorer Tools

Alarms, Events, and Audit-trail

Extended UNS using TagProvider Services

Historian, time-series data



Pillar 3: Application Modules Pillar 4: Operator UI

SQL Database Connections and Queries

Symbol Library extensions

Scripts and business logic (C#, VB.NET, Python 3)

Displays (Canvas & Dashboard) & UI Security 

Reports, data pub (PDF, CSV, HTML, XML & JSON)

Layouts,  Client deployment settings


Object Model Power

All configured objects inherit from .NET classes, providing native functionality without custom coding:


Tag.DateTimeExample.Value.DayOfWeek  // Returns Monday, Tuesday, etc.
Tag.DateTimeExample.Value.AddDays(7)  // Date arithmetic


Script.Task.Example1.LastCPUTime      // CPU usage tracking
Script.Task.Example1.LastExecutionTime // Performance metrics


This means you get hundreds of methods and properties automatically - no coding required!


Feature Highlights

Development Productivity

  • IntelliSense everywhere - Auto-completion for tags, objects, properties
  • Real-time validation - Red borders and tooltips for errors
  • Refactoring support - Rename with automatic reference updates
  • Cross-reference tools - Find all uses instantly
  • Keyboard shortcuts - Standard editing (Ctrl+S, F5, etc.)

Unified Configuration

  • Single environment - All modules in one interface
  • Consistent UI patterns - Same experience across modules
  • Context menus - Right-click relevant operations
  • Drag-drop support - Between panels and modules
  • Quick navigation - Jump to Home, Tags, Draw, Runtime

Testing and Validation

  • Test Mode - Run without leaving Designer
  • Online configuration - Modify running solutions
  • Simulation tools - Test without field devices
  • Build validation - Automatic error checking
  • Performance monitoring - Real-time resource usage


How It Fits in the Solution Lifecycle

Designer is the configuration workspace in the Solution Lifecycle:

  1. Solution Center - Create and manage solutions
  2. Designer ← You are here (Configure all modules)
  3. Runtime - Execute and monitor

Designer produces the configuration that Runtime executes. Test Mode lets you validate behavior before publishing to production.


Next Steps

Continue Learning

  • [Runtime (Concept) →] - Understand solution execution
  • [P1: UNS Foundation →] - Start building your solution
  • [The Four Pillars →] - Learn the methodology

Practical Guides

  • [Designer How-to Guide] - Step-by-step instructions
  • [Module Configuration] - Detailed module guides
  • [Test Mode Tutorial] - Testing best practices


In this section...