Overview
The software platform provides simple, optimized, and flexible workflows. Any configuration procedure can be done with a few clicks. This page contains information about the typical and additional procedures related to the solution configuration workflow.
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 solutions maintenance.
As explained in the Core Integrated Modules and Tools section, the platform has a modular architecture, therefore the Solution Configuration does not need to follow one specific sequence. Any module can be modified at any time independently.
So, you can start by configuring any solution module. You can begin by defining or importing tags, setting up external tags sources, mapping devices, structuring data templates and reviewing asset trees, drawing the displays, adjusting alarms, customizing security definitions, or configuring datasets and historians.
Configuration Workflow
Typical Solution Configuration Procedures
When you start, the most common procedure for new solutions is associated with the tags. While developing a solution, you should clearly understand the architecture you working with. In other words, you must know which data you will get and from which devices. Therefore, one of the first steps in solution development generally is related to the tags definitions.
However, different ways exist to define or import tags into your solution. You can create them from scratch. But you can import the tags definitions from an import file using the available Import Wizards. With the Import Tags Wizards, 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 more about the available import wizards, see the Import Tags Wizard.
These are typical procedures to follow:
| Typical Configuration Procedures | ||
|---|---|---|
Action | Where | Description |
Create Tags | Unified Namespace → Tags | The easiest way to create Tags is by Copy and Paste them from a sheet. But also you can define them one by one by clicking on New Tag on the toolbar or on the Asset Tree toolbar. |
Import Tags | Solution → Import Tags | Importing Tags, it may be useful to import tags wizards. |
Define ExternalTags source | Unified Namespace → ExternalTags Source | ExternalTags source can be used for dynamic data monitoring or Historian Database targets. |
Create Tag Templates | Unified Namespace → Data Templates | A well-defined data model 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 defined, performs a final organization of the Assets. |
Create Displays | Displays → Draw | Create display pages, popups and dialogs. |
Configure Devices | Devices | Setup the commutation channels with the field devices and map tags as needed. The Import procedure creating may had already defined this step. |
Adjust 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 Historian | Datasets | Setup connections to required SQL databases, define tables and queries that shall 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 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. |
Set up Reports | Reports | It is possible to save Displays as PDF or JPEG and use them as reports. Also, use the Reports module to created additional reports. |
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 | 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 to use categories to better organize the configuration objects. It also allows to select the default 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. |
Symbols customization | Displays → Symbol | Check the Symbol Library, and expand it as necessary to the Symbols required by your solution. Create Symbols mapping to your TagTemplates and your categories. Draw a diagram and information about the solution on the MainPage, which is the page that is showed at the solution Selector list. |
Review your Layouts | Displays → Layouts | The layout is the organization of your windows and displays. Toolbars and Sidebars are commonly used for navigation, and the remnant area are used for the working displays. |
Test the Solution | Runtime → Startup | Executes the solution in Test Mode to check its functionally. If there is a formal Validation procedure, use the Development and Validation profiles available at the Sandbox settings. |
Deploy the Application | Runtime → Startup | Runs the solution as production mode and execute the deployment procedure to the field computer. |
The Additional Configuration Tools section provides a number of powerful features that can be used to customize, manage, and troubleshoot solutions. These features can be helpful for users who want to create and deploy complex solutions.
In this section:
| Page Tree | ||||
|---|---|---|---|---|
|
...