Overview
The software platform provides simple, optimized, and flexible workflows. Any configuration procedure can be done completed with just a few clicks. This page contains detailed information about the typical and additional procedures related to the solution configuration workflows. Basics Basic workflows include creating and importing tags, setting up devices and alarms, and using templates for asset models.
On this page:
| Table of Contents | ||||
|---|---|---|---|---|
|
Modular Architecture
The modular architecture of the software platform enables a flexible workflow for the creation, management, deployment, and maintenance of solutions maintenance.
As explained in the Modules and Tools section section, the platform has a modular architecture, therefore meaning the Solution Configuration does not need to follow one a specific sequence. Any module can be modified at any time independently.
So, you You can start by configuring any solution module. You For example, you can begin by defining or importing tags, setting up external tags tag sources, mapping devices, structuring data templates and , reviewing asset trees, drawing the displays, adjusting alarms, customizing security definitions, or configuring datasets and historians.
Basic Workflows
Data
definitionsDefinitions (Unified Namespace and Data Explorer)
Use the Unified Namespace module for asset modeling. Define your asset model to represent your asset structure, their relationships, and metadata. Interact with this model using the Asset Tree to navigate into the asset structure. Use data templates and enumerations to model your data . Define your and define custom data types. Leverage the Data Explorer tools for browsing and discovering relevant data points from devices.
Process
modulesModules (Devices, Alarms, Historian)
Use the Devices module to connect to field devices and configure communication protocols to enable data flow. Define the rules to trigger alarms and events, and log them alongside changes and user actions for analysis and troubleshooting. Integrate the time-series historian , by configuring data collection and aggregation.
Application
modulesModules (Datasets, Scripts, Reports, Displays)
Use the Datasets modules module to establish connections to external SQL databases for additional data storage and integration. Use the Scripts module to allow customization customize through scripting to perform , allowing for complex data transformations and calculations. Use the Graphical tools for building graphical tools to build dashboards, visualizations, and reports, turning raw data into actionable insights.
Runtime and Management (Runtime, Security, Track Changes)
Put your solution into the live production environment and begin continuous data collection and analysis. Use the Security module to implement user authentication and role-based access control to protect data integrity. Use Use the Track Changes module to log all configuration changes, providing traceability and aiding in troubleshooting.
Typical Solution Procedures
When you startstarting a new solution, the most common initial procedure for new solutions is associated with the tagstag definitions. While developing a solution, you should it is crucial to clearly understand the architecture you are working with. In other words, you must know which data you will get and from which devices, including the data sources and devices involved. Therefore, one of the first steps in solution development is generally is related to the defining or importing tags definitions.
However, There are different ways exist to define or import tags into your solution. You can create them from scratch . But you can import the tags or import tag definitions from an import file using the available Import Wizards. With the Import Tags WizardsWizard, you can access all of the data from your devices with just a few clicks. After that, you can start using them in your solution. To read learn more about the available import wizards, see the Import Tags Wizard.
These are the typical procedures to follow:
Typical Configuration Procedures | ||
|---|---|---|
Action | Where | Description |
Create Tags | Unified Namespace → Tags | The easiest way to create Tags tags is by Copy copying and Paste pasting them from a sheetspreadsheet. But also However, you can also define them one by one by clicking onNew Tag on in the toolbar or on the Asset Tree toolbar. |
Import Tags | Solution → Import Tags | Importing Tags , it may be useful to import tags wizardsfrom external sources. |
Connect External Tags sourceTagProviders | Unified Namespace → External Tags SourceTagProvider Connections | TagProviders ExternalTags source can be used for dynamic data monitoring or as Historian Database targets. |
Create Tag Templates | Unified Namespace → Data Templates | A well-defined data model greatly simplifies a lot the solution development. It creates templates not only to represent your assets , but also for data structures intended to implement internal solution logic. |
Review Assets tree | Unified Namespace → Asset Tree | With the Templates and ExternalTags source TagProviders defined, performs perform a final organization of the Assets. |
Create Displays | Displays → Draw | Create display pages, popups and dialogs. |
Configure Devices | Devices | Setup Set up the commutation communication channels with the field devices and map tags as needed. The Import import procedure creating may had have already defined this step. |
Define Alarms | Alarms | Configure your alarm groups, areas, and tags events generating alarms. |
Configure Historian | Historian | Configuration of the Historian module is accomplished through the following sections: Target Database, Historian Table, and Historian Tag. |
Configure Datasets | Datasets | Setup Set up connections to required SQL databases, and define the tables and queries that shall will be used. |
Customize Security | Security | The Security module ensures the safety and integrity of your solutions by managing user access, roles, and permissions. It allows administrators to control who can access, view, and modify solution components and , as well as manage runtime user interactions with displays and actions. |
Modify Scripts | Scripts | Create function libraries at Scripts → Classes and server side solution logic using Scripts → Tasks. |
Configure Reports | ReportsIt is possible to save Displays as PDF or JPEG and use them as reports. Also, use the Reports module to created additional reports. | Create Text and PDF reports. You can also generate WebData definitions to manipulate JSON, HTML, Text and XML data. |
Additional Configuration Tools
The Additional Configuration Tools section of the Solution Designer provides a number of features that can be used to customize and manage solutions. These features include the ability to:
Customize Solutions Settings
Define Categories on large applications
Import Plugins
Manage Solution Plugins
Export the Solution Configuration
Access the Solution History
In addition to these features, the Additional Configuration Tools section also provides a number of procedures that can be used to test, deploy, and troubleshoot solutions. These procedures include:
Additional Configuration Procedures | ||
|---|---|---|
Action | Where | Description |
Setup Family and Model | Solution → Settings | Correct definitions of the Product Family and Model correct definitions are essential, as the Solution Designer will present or limit configuration options based on those settings. |
Create Categories | Solution → Categories | For large size solutions, it is recommend recommended to use categories to better organize the configuration objects. It This also allows you to select the default Symbols symbols used to represent the tags in the graphical displays. |
Import Plugins | Solution → Import Plugins | Importing Plugins , it may be helpful to import Plugins at Solution → Import Plugins(encapsulated solution components). |
Symbols customizationCustomization | Displays → Symbol | Check the Symbol Library , and expand it as necessary to include the Symbols symbols required by your solution. Create Symbols mapping symbols mapped to your TagTemplates and your categories. Draw a diagram and provide information about the solution on the MainPage, which is the page that is showed at the solution displayed in the Solution Selector list. |
Review your Layouts | Displays → Layouts | The layout is refers to the organization of your windows and displays. Toolbars and Sidebars sidebars are commonly used for navigation, and while the remnant remaining area are is used for the working displays. |
Test the Solution | Runtime → Startup | Executes Execute the solution in Test Mode to check its functionallyfunctionality. If there is a formal Validation validation procedure, use the Development and Validation profiles available at in the Sandbox settings. |
Deploy the Application | Runtime → Startup | Runs Run the solution as production mode in Production Mode and execute the deployment procedure to the field computer. |
. |
In this section:
| Page Tree | ||||
|---|---|---|---|---|
|
...