Skip to main content
Version: Next

User Guide

Use this section after you complete Getting Started or after you already know how to open Editor and create a basic project.

The goal of this section is not to replace the quick start. It helps you extend your first project with clearer module-by-module instructions.

Start Here

Use this section when you want to:

  • understand one module in more depth after your first project runs
  • follow a more detailed path for projects, tags, views, alarms, and data
  • move from a simple demo to a reusable engineering workflow
  • look up the correct module after you already know the task you want to complete

What This Section Assumes

Before you spend time here, make sure:

  • Editor can open normally
  • you can create or open a project
  • you understand the difference between Editor and Vision
  • you have at least one working tag path, or you know whether you will start with internal tags, a real device, or Static Simulation

If not, complete Getting Started first.

If you want copy-ready names, values, thresholds, users, and recipe examples while following the module guides, keep Configuration Sample Data open in another tab.

For a new engineer, the most practical order is:

  1. Working with Projects
  2. Understanding Tags
  3. Creating Internal Tags or Creating External Tags
  4. Understanding Views
  5. Creating Monitoring Views
  6. First Success Checkpoint
  7. Understanding Alarms and Creating Alarms
  8. Understanding Data Management and Creating Data Tables

Choose the Right Path

If your main goal is a first working HMI

Follow this order:

If your main goal is dashboards and reporting

Start here after the basic HMI path works:

If your main goal is maintainability

Focus on:

Suggested Learning Rhythm

For the best onboarding experience:

  • finish one small project first
  • use the same example project while reading the deeper guides
  • reuse Configuration Sample Data instead of inventing a new dataset for every page
  • treat First Success Checkpoint as the end of the first real onboarding milestone
  • add alarms only after live values are verified
  • add historian or data tables only after the monitoring view already runs
  • treat scripts, permissions, language, and application components as stage-two topics

After the Core Path

Once the project, tags, views, alarms, and data path makes sense, continue with: