Overview
The software platform optimizesprovides simple, simplifiesoptimized, and flexibly streamlines all workflows related to solution configuration proceduresflexible 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 an adaptable workflow for the creation, management, deployment, and solutions maintenance.
As explained in the Platform Overview section, the platform has a modular architecture, therefore the Project Configuration does not need to follow one specific sequence. Any module can be modified at any time independently.
Configuration Workflow
Typical Solution Configuration Procedures
When you start..
For example, when developing a solution, you should have a clear understanding of the architecture you will be 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 is related to tags and devices.
However, there are different ways to start defining tags or mapping devices in your solution. You can map them from scratch. 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.
There is a typical procedure to follow.
| Typical Configuration Procedures | ||
|---|---|---|
Action | Where | Description |
Additional Configuration Tools
Verify the Target Platform and customize settings.
- Customize Settings, if needed
- Define Categories on large applications
- Import Tag Definitions , when applicable
- Manage Project Plugins, when applicable
- Export the Project Configuration
- Access the Project History
Additional Configuration Procedures | ||
|---|---|---|
Action | Where | Description |
Setup Family and Model | Project Settings → General | Product Family and Model correct definitions are essential, as the Project Designer will present or limit configuration options based on those settings. |
Create Categories | Project Settings → Categories | For large size projects, 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. |
Create Tag Templates | Unified Namespace → Data Templates | A well-defined data model simplifies a lot the project development. It creates templates not only to represent your assets, but also for data structures intended to implement internal project logic. |
Add Tag Providers | Unified Namespace → Asset Tree or | Tags Provider can be used for dynamic data monitoring or Historian Database targets. |
Create or Import Tags | Unified Namespace → Asset Tree or | In addition to importing Tags, it may be useful to import Plugins at Project Settings→ Import Plugin. |
Review the Assets tree | Unified Namespace → Asset Tree | With the Templates and Providers defined, performs a final organization of the Assets. |
Historian configuration | Historian | Configuration of the Historian module is accomplished through the following sections: Target Database, Historian Table, and Historian Tag. |
Security definition | Security | The Security module ensures the safety and integrity of your projects by managing user access, roles, and permissions. It allows administrators to control who can access, view, and modify project components and manage runtime user interactions with displays and actions. |
Devices setup | Devices | Setup the commutation channels with the field devices and map tags as needed. The Import procedure creating may had already defined this step. |
Alarms setup | Alarms | Configure your alarm groups, areas, and tags events generating alarms. |
Datasets setup | Datasets | Setup connections to required SQL databases, define tables and queries that shall be used. |
Scripts setup | Scripts | Create function libraries at Scripts → Classes and server side project logic using Scripts → Tasks. |
Symbols customization | Displays → Symbol | Check the Symbol Library, and expand it as necessary to the Symbols required by your project. Create Symbols mapping to your TagTemplates and your categories. Draw a diagram and information about the project on the MainPage, which is the page that is showed at the Project 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. |
Create the Displays | Display Drawing | Create display pages, popups and dialogs. |
Create 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. |
Test the Project | Runtime → Startup | Executes the project 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 project as production mode and execute the deployment procedure to the field computer. |
In this section...
| Page Tree | ||||
|---|---|---|---|---|
|
...