The project menu is located at the top right-hand side of the screen.
Image Modified
Figure 69. Project Menu...
Note: Baselines with only a subset of the complete project breakdown can only be compared against other baselines of the same branch – one cannot compare them with the entire structure.
Image Modified
Figure 71. Version comparison window...
- to display and browse a baseline in the breakdown structure pane,
- to export a baseline as an EDMtruePLM specific ISO 10303-239 P21 file including all files and a separate reference data P21 file (for details of the contents of the resulting zip-file, see chapter 4.1.5 "Download STEP pack") and
- to delete baselines.
Image Modified
Figure 72. Baseline tab...
Three search 
methods are available for finding breakdown elements / nodes and documents in the breakdown structure. There is a "Quick search" for nodes and more detailed search specifications for nodes and for documents. A search will be executed on the selected product breakdown version. So, if you need to search within a specific version of the breakdown, you must select the version first. Start search by the search icon in the project menu at the top right corner, as shown below. The system allows 'wildcard' search for all three types of searches.
Image Modified
Figure 73. Search tab...
"Quick search" finds breakdown elements / nodes based on the following filters. As its name indicates it is quicker than "Node search", but not as sophisticated.
Image Modified
Figure 74. Quick Search"Node search" offers additional filters (see Figure 75). For large data sets it is time-consuming.
Image Modified
Image Modified
Image Modified
Image ModifiedFigure 75. Node searchThe different "Node search" tabs are explained in the following bullet points.
...
Use the document search form shown in the two figures, below, to find documents in the breakdown structure. The form consists of five tabs, which are explained in the following sub-sections.
Searches are done on the selected product breakdown version. So, if you need to search within a specific version of the breakdown, select that version first.
Image Modified
Image Modified
Image Modified
Figure 76. Document search 1
Image Modified
Image ModifiedFigure 77. Document search 2...
- Document search result tab
Image Modified
Figure 78. Document search resultThe following functions are available for each document within the search result tab:
...
In addition, by clicking on the search result, the properties of that document are loaded into the document properties window.
- Node search result tab
Image Modified
Figure 79. Node search resultBy clicking on the search result menu, you can go to the position of the node within the breakdown structure. In addition, by clicking on a search result item the properties of the selected node are displayed within the breakdown properties window.
...
Search results can be sorted alphabetically by right-clicking on the search result tab and selecting the "Sort"-option.
Image Removed
Image Added
Figure 80. Sorting search result...
Products and Organizations are managed in the Catalogues 
menu item. Products and Organizations are considered reference data.
Image Modified
Figure 81. Catalogues...
This version of EDMtruePLM offers support for representing products and their relations to breakdown elements. Types of products may be created and may then be pasted into one or several breakdown elements.
Before creating products, confirm that reference data have been defined for "Product element type", "Product stages" and "Product domains" in the reference data GUI. To add a product, click on the +-sign as shown in the figure, below.
Image Modified
Image Modified
Figure 82. Product menuProperty values cannot be changed after product creation; delete and re-create instead.
For relating products to breakdown elements, see in chapter 3.4.2.3.6 Put Product.
...
To create an organisation, select "Organisation" from the Catalogue menu, click on the +-sign and fill in the form.
The form consists of information such as Organisation name, Unique id (Uid) and Address as shown below. Property values may be changed after creation.
Image Modified
Image Modified
Figure 83- Organisation menuFor relating organizations to breakdown elements, see in chapter 3.4.2.3.5 Add Organisation.
Reference data definitions
...
The "Reference data" page allows the user to manage project metadata. These metadata are a powerful method to configure the system for different uses and processes.
Image Modified
Figure 84. Reference dataThe system allows the user to define values for the following metadata types (refer Figure 84):
...
To change or add metadata to the system, use the 
icon in a selected reference data type menu. All metadata except for Breakdown properties, Document properties, Product properties, Requirement properties and Aggregate struct elements define new metadata by adding a new value to the form below.
Image Modified
Figure 85. Add reference dataAs an example, the project manager can define as "Source of information" different types of source categories, e.g., internal data, customer data, public data etc. .
...
The system will allow metadata to be removed only if it is not used in a project. Metadata that can be removed have an 
icon in front of them. The remove icon can be used to remove the metadata (see Figure 86).
Image Modified
Figure 86. Delete reference dataNote: The system will not allow a metadata to be deleted if it is in use, this will guarantee that the data will not become corrupted by removing the used metadata.
...
This item allows the user to extend the EDMtruePLM system by creating additional properties (metadata) for documents. To add a new document property, click on the 
icon and fill in the form; this is similar as for breakdown properties, see Figure 91, below.
Image Modified
Image Modified
Figure 87. Add document propertyDocument properties may be of different data types, such as text and numbers. The input forms vary depending on the requested data type; see Figure 87, above.
The property types are explained in Table 5, below.
The "read only access" option allows a user to create properties the values of which can only be changed by the project manager.
Table 5. Document property typesType | Definition |
Text | String value property |
Numeric | Numeric value property. Provide a name and a unit of measure |
Date | Date time values |
Enumeration | An enumeration type property consists of a list of pre-defined values. Provide the property name and the values of the enumeration; values are separated by comma. |
Boolean | True/false property |
Adding breakdown element type
Breakdown element types may be defined as a class hierarchy where subtypes inherit the properties of their parents. The process starts with the interaction in Figure 88. Selecting the upper-most +-sign will trigger the user interaction in Figure 89 to add a new top level breakdown element type. The smaller +-signs enable the definition of subtypes of existing element types.
Image Modified
Figure 88. Add breakdown element subtype
Image ModifiedFigure 89. Add breakdown element type...
Breakdown properties are defined per type of breakdown element; subtypes inherit from their parents.
Image Modified
Figure 90. Add property for specific breakdown element typeAfter selecting the breakdown element type that the property shall become a part of click on the
icon to create a breakdown property; see Figure 91, below.
Image ModifiedFigure 91. Breakdown property input formBreakdown properties may be of different data types, such as text and numbers, similar to the document properties described above. The input forms vary depending on the requested data type; see Figure 92, below.
The property types are explained in Table 6, below.
The "read only access" option allows a user to create properties the values of which can only be changed by the project manager.
Image Modified
Image Modified
Figure 92. Create new breakdown element property Table 6. Breakdown element property typesType | Definition |
|---|
Text | String value property |
Numeric | Numeric value property. Provide a name and a unit of measure |
Date | Date time values |
Enumeration | An enumeration type property consists of a list of pre-defined values. Provide the property name and the values of the enumeration; values are separated by comma. |
Boolean | True/false property |
Serial | This is a sequence number. When a node with such a type of property is created, the system checks for the last given sequence number, increases it by 1 and assigns it to the newly created node. If the node is the first occurrence of its type, the value 1 is assigned. |
Formatted serial | This is a text property that represents a sequence number with some textual prefix/suffix. An example is 'SN:00012345', where 12345 is a value of a property of type sequence (see above) or an implicit sequential number calculated like the sequence number, but used only in the context of the property typed formatted_serial. The format of the property representation must be stored in a parent property named "<name_of_child_property>-format". The sequence number must follow the formatting code of the C programming language; the default formatting value is '%010d' (to produce strings like '0000000012' or '0000065412').
E.g. a child breakdown element has a property by name 'XXX' and of type formatted_serial. Its parent is given the text property 'XXX-format'. In case XXX-format = 'S/N:%06d' the 123rd instance of the child node receives the property name and value pair XXX = 'S/N:000123'.
Note: formatted_serial as well as sequence type properties use node type specific counters that are valid over the whole target model and not only in the domain of a single parent. |
Counter | This is a numerical counter of the children of a parent node. Child nodes with a property typed as Counter will at creation time be assigned a numeric value that is the number of children of their parent node. |
Formatted Counter | This is a textual representation of the Counter property type, alike Formatted_serial described above. The format of the representation must be stored as a parent node property. The format is composed of two pieces: prefix (value of parent property with the same name) and format of counter representation (should be stored in parent property named '<child_property_name>-format'). The property can be used to generate hierarchical counters, like 'XXX.012.001.01' for child of node 'XXX.012.001'...
E.g. a parent has the property 'ID' of type formatted_counter with value 'XXX.012' and textual property 'ID-format' = '%s.%02d'. A newly created child node (7th one) receives 'ID' = 'XXX.012.07' as well as a copy of 'ID-format' = '%s.%02d' of its parent.
Note 1: <child_property_name>-format may be undefined.
Note 2: The default format string is '%s.%3d'. |
Extended Counter | This is a reserved type of counter for future use. It works exactly like formatted_counter with the only difference that the default format value is '%s.%03d' |
Adding derived property
A derived property calculates its value from other properties.
The icon 
is for the creation of the derived property and is located in the breakdown element and document property creation area; see Figure 91, above.
Figure 93. Create derived propertySelect the property data type from the drop-down list and give a name to the new derived property (see Figure 93). To create the derived property value pattern, add the properties from the
Property drop-down list and click on the
Add button. The drop-down list contains all local properties, that is, only the properties of the current document or breakdown element type.
Image ModifiedFigure 94. Derived property exampleEach selected property will be shown as an argument to the
ATTR () method. To add static text or a delimiter between the values, place the text between single quotes, see Figure 94 above. To create the derived property, click the OK button.
...
An aggregate structure is an array of value sets of the same type. It is intended to store streamed sensor values.
To add an aggregate structure, first create an aggregate structure type and afterwards add types of elements to it. To create a new structure type, click on the "Aggregate struct" in the reference data menu and create a new structure type by clicking on the 
icon. After having created the structure, go to "Aggregate struct elements" from the reference menu and select the new structure type from the drop-down list.
Image Modified
Figure 95. Aggregate structureUse the
icon to add new elements to the structure.
Image ModifiedFigure 96. Create new aggregate property type You can add the following types of elements to the structure:
Table 7. Aggregate property typesType | Definition |
Text | String value property |
Numeric | Numeric value property. Provide a name and a unit of measure |
Date | Date time values |
Enumeration | An enumeration type property consists of a list of pre-defined values. Provide the property name and the values of the enumeration; values are separated by comma. |
Boolean | True/false property |
Adding a filter key to aggregate data
To be able to filter the aggregate data, EDMtruePLM provide the functionality to assign an element in the aggregate structure as primary key. To assign an element as the key to an aggregate type, click on the 
icon in the same row (see Figure 97).
Image Modified
Figure 97. Aggregate typeAfter selecting an element as the key to the aggregate type, the word "
Key" is added to the "Type" string of the element.
...
The language selector allows the user to change the user interface language as shown below between English and Norwegian.
Image Modified
Figure 98. GUI language selection