Project structure
Copy a row and its underlying structure
Changing the 'Structure id' by altering the structure of the tree
Tag code based on tag code format
In this window it is possible to create a tree that can contain Product and Tag information.
This can be done by adding sub-rows, and drag/drop the rows above/below each other. Each row or sub-row can have Product and Tag information.
If a row is created, a Product can be assigned by selecting a Product from the dropdown list. When a Product is selected, a 'new' Product is assigned to the row which inherits all the Modules, Attribute, I/O etc., from the Library. After selecting a Product, the Product can be configured in the Configure popup window (via Configure button or context menu) or in the 'Product Details' detail window. With the help of the detail window you can navigate trough the Attributes, I/O items and Modules of the selected Product. This way, you can fill in Attribute data for example. If you want to fill in a large amount of Attribute data, we advice to use the Engineering window.
In a Project there is the Reference id. This is a unique number for every structure which can never change in the Project. This is mainly used for importing data in the Engineering window or the Project structure window.
Note: By default not all columns are shown. Please look inside the column chooser for other possible columns.
Example of a flat tag list
Example of a Product structure
Icons
|
Row without a Product. |
|
Product in row has a valid configuration. |
|
Product in row has an invalid configuration. |
|
Product in row has a valid configuration, but at least on sub-row has an invalid configuration. |
See also:
Click New.
Select a new row or new sub-row.
Optionally give it a unique Tag id.
Select a Product by selecting it from drop down list.
When a row is selected and a new row is created, the new row will be added on the same level as the selected row.
When a row is selected and a new sub-row is created, the new row will be added as a sub-row of the selected row.
New sub-row can be created, with a maximum of 10 rows nested inside each other.
When a Product is selected, any newly added Sub-products are marked with a 'green' color.
When adding a new Product (with or without sub-products) the previous 'green' Sub-products will no longer be 'green'
Notes:
The Structure code cannot start with 'Hardware product'.
The Structure code must be unique within its own level.
The Tag id must be unique.
If the newly selected Product has Sub-products in the library, these Sub-products are automatically added. If the Structure code of a Sub-product results in a duplicated Structure id, the Structure code is not transferred from Library to Project.
Click Copy.
The selected row and its underlying structure will be copied.
The copied structure code gets the text ' - Copy (x)' attached to it as a suffix, where 'x' is the number of copies made.
The copied Tag id gets the text ' - Copy (x)' attached to it as a suffix, where 'x' is the number of copies made.
Select the row(s) to delete.
Click .
Click in the message dialog.
It is possible to delete multiple products without changing the structure. This can be done by:
Select the row(s) to delete.
Right-click and select .
To change the structure, simply drag them up and down the tree. By doing so the Structure id is automatically changed.
The Structure id is an id that is created based on the position in the tree in combination with the Structure code.
If a value is entered in the Structure code, that value will be used to identify/create the id inside the Structure id.
The Structure id is always separated by a '.' (dot) and can therefore not be used inside the Structure code.
See example:
In the above example you see that the Structure code 'M1' replaces the old value of '1' in its own Structure id and the items below it.
Structure id changes when:
The Tag code can be edited manually, but it is also possible to select it based on the selected Tag code format. When the Tag code name contains a numeric placeholder ('#') the placeholder will be selected and simply replaced by the correct number from the users input.
The Tag id can be edited manually, but it is also possible to generate it, based on the selected Tag structure format. This can be done by using the right click option on a row (multiple rows can be selected), and clicking 'generate tag id'. The Tag id is generated conform a format.
It is also possible to restructure the Tag id, which will find/create a the new structure for a new Tag id. This could be very useful if a Tag id is given into a single row, but is actually multiple levels. Or when a Tag id is changed and therefore must be relocated.
Notes:
In the configuration popup, the selected Product can be configured by selecting Attribute values.
Selecting a value, automatically selects the corresponding Modules, Typicals and Attributes.
Changes in the configuration popup are directly updated in the detail window ‘Product details’ and vice versa. In a few mouse clicks the Product is fully configured.
In the View all mode, you can see all the Interfaces, Attributes, Modules and Values set, even if they are net selected for the selected Product.
The left side of the detail window ‘Product details’ shows the configuration of the Product. From here you can navigate through all the Attributes and Modules which are selected for this Product. The right side of the Detail window ‘Product details’ shows different content, dependent on what is selected in the tree. For an example, if the ‘Attributes’ row is selected, it will show all the Attributes of the Product in a grid. The values of the Attributes can here be edited. If the Product has no Attributes, or not a single Attribute is selected, the Attributes row will not be visible.
Here you can create a structure of the Project, a Sructure row can have a Product.
Here you see the actual configuration of the Product.(Only the items that are selected in the configuration are shown).
Here you can modify values of the Product (e.g. Attribute values).
Document, Logical Scada and Electrical modules with an I/O-link only appear in detail window 'Module' when the Module and it's related I/O item are selected both.
See also:
It is possible to import a Project Structure based on a different id's. (Tag id, Structure id, Ref id, Ext. ref id).
This import is done by using an Excel file.
To Import products:
Click Import/Export.
Choose 'by Structure id', 'by Tag id', 'by ref. id' or 'by Ext. ref id'.
In the pop-up window click Import.
Browse for an Excel file to import and click Open.
Review changes and click OK to accept them or Cancel to cancel the import.
Clicking the main button will start the import/export for the last chosen import/export type. When clicking the arrow on the right side of the button.
Any import/export type can be chosen, this will be saved in the user settings.
Importing by Tag id will create a structure which can be defined in the Tag structure format in library.
For example import see: Example Tag Id Import.
Importing by Structure id will create a structure which is separated by a dot '.' each dot will be an new level in the structure.
See example (from Excel to Typical Manager)
The different importing methods all have their own advantages, see them described separately:
Import/Export by Tag id.
Import/Export by Structure id.
Import/Export by Ref id.
Import/Export by External ref. id.
NOTE:
When changing the Structure id or Tag id, the Project structure will not be changed (the Product is not moved within the structure)
When importing a Product that has Sub-products in the Library, these Sub-products are automatically added. If the Structure code of a Sub-product results in a duplicated Structure id, the Structure code is not transferred from Library to Project.
When importing a Panel, that Panel will also be related to the Sub-products specified in the Library with the imported Product
See also:
Importing/Exporting by Tag id is the most commonly used method to exchange data between Typical Manager and external tooling.
When using a Tag structure format, it is possible to take apart the Tag id and create a Tag based structure, and separate Tag codes for each level. See: Tag Structure format
When importing by Tag id, it is possible to import the following values:
Importing by Structure id will create a structure which is separated by a dot '.', each dot will be a new level in the structure.
When importing by Structure id, it is possible to import the following values:
If you want to have your (Tag) rows in a structure, but you cannot use the Tag structure format to create this structure, maybe this method can fit your needs.
It is possible to import new rows based on the Structure id. (in this case, use import by Structure id).
Also the Project structure can be changed by importing the Structure Id. (In this case, use import by Ref. id to change the Structue id of existing rows)
In the images below, different examples how an import will change the Project structure:
Moving Project rows (Tags) into a parent row.
Moving Project rows (Tags) to a different position in the structure.
Moving Tags out of the structure, without the remaining Tags to be moved, (note the 2 project rows created, to do so).
The 'Ref id' is a fixed unique id for Project rows in Typical Manager.
This Id can be used for changing the Tag id or Structure id, or for example, to exchange data with external software when the Tag id/ Structure id isn't reliable enough, since the Ref id can't change in the entire lifetime of the Project row.
When importing by Ref id, it is possible to import the following values:
Using an External reference id (Ext. ref id) for Import export, can be useful when Project rows (Tag id's) are defined by external Software like Autocad P&ID/ Revit/etc.
When your Project rows need to be updated because of changes, It's possible that Tag id's are changed or obsolete.
The Ext. ref id can be set when importing by Tag id, Structure id or Ref id.
It is also possible to import new rows based on the Ext. ref id, in this way it's not possible to create a Structure based on Structure id, or the Tag code structure format.
Best practice: Import by Tag id (In this way ,the Tag id can be set and a structure can be made with help of the Tag structure format). In the same time the Ext. ref id can be imported to have a connection with your external software.
When importing by Ext. ref id, it is possible to update the following values:
This can be done by adding Attribute columns to the imported file, the attributes will be validated in the same way as in the Engineering view
It is only possible to import Attributes from a Product, it is not possible to import Attribute values directly into Modules (Electrical, Logical etc.)
It is also possible to import Configurations. A Configuration is recognized as Configuration when it is imported in a column the value 'Configuration' in the header. The format for a configuration value is <attribute value> (<attribute name>). Example as shown in the image below: True (Supply: 24Vdc).
Notice also the orange icon at the begin of the imported rows, as a reminder that the configuration is not complete yet, the not imported Selection list, has not been assigned a value.
See also:
In many projects where Typical Manager is used, a Tag list is created from outside Typical Manager. Often Tags are moved/changed or even removed.
When Tags are removed from the import list and that list is imported into Typical Manager these Tags will be shown as obsolete Tags.
The purple row will indicate the Tag id that was not present in the import file. As any import status, the obsolete values can be filtered using the filter checkbox.
There are three actions possible for obsolete rows.
'Keep', this is the default, and will keep the row in Typical Manager, just like before when not-imported rows which already exist in Typical Manager still where in Typical Manager after the import.
'Delete', by setting the 'Action to obsolete item' to Delete the Tag will be removed from Typical Manager. If a Tag contains sub-rows in Typical Manager or in the import (which are not obsolete), then can a Tag not be deleted. 'Replace by', this will replace the obsolete Tag by a Tag in the imported list of the users choice.
