Overview
Content
On this page:
<< This Page has to created again, using the new concepts of DataExplorer, UnifiedNamespace, ServerModules, and DisplaysClients>>. And mention ClientProjects
Modular Architecture
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 Project Configuration Steps
<<<<. This is too complex. It needs to be a simpler workflow, and then have more options in the section 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
There is a typical procedure to follow.
Typical Project Configuration Steps | ||
|---|---|---|
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 | |
Security definition | Security | |
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. |
Additional Configuration Tools
In this section...