Versions Compared

Old Version 2

changes.mady.by.user admin

Saved on

compared with

New Version 3

changes.mady.by.user admin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comprehensive reference showing

Solution Lifecycle (Reference): information on how FrameworX platform features support each phase of the solution lifecycle.

This page connects project management concepts with specific platform tools and capabilities.→ Concept | How-to Guide | Reference

On this page:

Table of Contents
maxLevel2
minLevel2
indent10px
excludeSteps
stylenone


Platform Components

The Solution Lifecycle

leverages

uses these integrated FrameworX components:

ComponentPlatform FeaturesPrimary Use
Solution CenterSolution management, templates, licensingProject creation and management
DesignerConfiguration IDE, diagnostics, Track ChangesDevelopment and testing
RuntimeExecution profiles, Build & Publish, monitoringValidation and production
DevOps & Version ControlGit integration, change tracking, audit trailChange management and deployment
→ Detailed documentation in child pages below

Project Planning with Four Pillars

Requirements Template by Pillar

Map

your

requirements

directly

to FrameworX architecture:

PillarRequirements FocusPlatform Configuration
P1: UNS FoundationData points needed<br>Equipment hierarchy<br>Naming standardsTags to create<br>Templates (UDTs) to design<br>Asset tree structure
P2: Process ModulesField devices to connect<br>Alarm conditions<br>Historical data needsDevice channels & protocols<br>Alarm items & groups<br>Historian tables & retention
P3: Application ModulesBusiness logic required<br>Database integration<br>Reporting needsScript tasks & classes<br>Dataset connections<br>Report templates
P4: Operator UIUser roles & screens<br>Client deployment<br>Mobile accessDisplay pages & navigation<br>Security configuration<br>Client types

Stakeholder Mapping

StakeholderFrameworX InteractionAccess Level
OperatorsRuntime displays, alarm managementClient access
EngineersDesigner configuration, diagnosticsEngineering license
ManagersDashboards, reportsView-only access
IT SupportSolution Center, Runtime monitoringAdmin access

Testing with Platform Tools

UNS Integrity Verification

The Unified Namespace is the foundation - verify it

Verify foundation first:

  1. Designer Test Mode (F5)
    • Validate tag structure and values
    • Test templates and instances
    • Verify asset tree navigation
  2. Property Watch
    • Monitor real-time tag updates
    • Check quality and timestamps
    • Validate calculations
  3. Diagnostics Tools
    Use
      • Runtime → Diagnostics for data inspection
      • Cross-reference verification
      • Module status monitoring

    → See [Designer (Reference)] and [Runtime (Reference)] for tool details

    Execution Profile Testing

    Test

    your solution

    across environments using built-in profiles:

    ProfileUsePlatform Features
    DevelopmentInitial testingLocal databases, full diagnostics, simulation
    ValidationSystem testingTest servers, limited clients, performance monitoring
    ProductionLive operationProduction databases, redundancy, optimized logging
    →

    Configure in Runtime → Execution Profiles

    Deployment Using Platform Features

    Build & Publish System

    FrameworX provides built-in deployment tools:

    1. Development Build
      • Runtime → Build & Publish
      • Create .dbsln for testing
      • Include debug information
    2. Production Publish
      • Create read-only .dbrun file
      • Version numbering
      • Release notes
    3. Deployment Package
      • Solution file
      • Execution profile
      • Client configurations

    Backup & Recovery

    Platform features for deployment safety:

    • Solution Backup: Before any deployment
    • Automatic Backups: Configurable schedule
    • Version History: Through Git integration
    • Rollback Capability: Previous .dbrun versions

    → See [DevOps and Version Control (Reference)] for Git integration

    Quality Gates

    Platform Checkpoints

    Use these FrameworX tools to verify quality:

    GatePlatform VerificationTool Location
    Build SuccessSolution compiles without errorsRuntime → Build & Publish
    No Unused ObjectsClean configurationTrack Changes → Unused Objects
    References ValidAll cross-references verifiedTrack Changes → Cross-Reference
    Test Mode PassRuns without errorsDesigner → Test Mode (F5)
    Performance CheckMeets requirementsRuntime → System Monitor

    Change Management

    Platform Change Tracking

    FrameworX automatically tracks:

    Change TypePlatform TrackingAccess Location
    Configuration changesTrack Changes logTrack Changes → Recent Changes
    User actionsAudit trailBuilt into all modules
    Version historyGit exportSolution → Export (if enabled)
    Build versionsBuild historyRuntime → Build & Publish

    Recommended Workflow

    1. Enable Git Integration
    (recommended)
      • Automatic JSON export
      • Version control ready
      • Diff-friendly format
    2. Use Track Changes
      • Monitor all modifications
      • Impact analysis before changes
      • Audit trail for compliance

    → See [DevOps and Version Control (Reference)] for setup

    Support & Maintenance

    Platform Diagnostic Tools

    Issue TypeFrameworX ToolLocation
    Communication problemsModule InformationRuntime → Diagnostics
    Performance issuesSystem MonitorRuntime → System Monitor
    Configuration errorsOutput windowDesigner (bottom panel)
    Tag issuesProperty WatchRuntime → Diagnostics
    Historical data gapsHistorian statusRuntime → Module Information

    Maintenance Features

    • Online Configuration: Changes without stopping runtime
    • Hot Updates: Apply modifications to running system
    • Remote Diagnostics: Connect Designer to remote runtime
    • Automatic Recovery: Self-healing connections

    Best Practices Checklist

    Leverage Platform Features

    ?
    •  Use Execution Profiles for environment management
    ?
    •  Enable Track Changes for audit trail
    ?
    •  Implement Git integration for version control
    ?
    •  Use Build & Publish for controlled deployments
    ?
    •  Monitor with built-in diagnostics

    Avoid Common Pitfalls

    ?
    •  Skipping Test Mode validation
    ?
    •  Not using execution profiles
    ?
    •  Ignoring Track Changes warnings
    ?
    •  Deploying without Build & Publish
    ?
    •  Missing backup before deployment

    See Also

    Child Pages

    [] - Solution management interface
    [] - Development environment and tools
    [] - Execution environment and diagnostics
    [] - Change tracking and Git integration

    Related Topics

    [] - Understanding the three stages
    [How-to ] - Step-by-step procedures
    [] - Architecture frameworkComprehensive templates and reference materials for managing FrameworX solutions through development, validation, and production stages using platform-specific tools and features.



    In this section
    :
    ...

    Page Tree
    rootV10:@self@parent
    spacesV1093DRAF