Show only results for:









Packaging

Packaging allows you to include / exclude objects of a model and save the selection in an .xlsx or .json file. This can be very handy if you want to give different versions / parts of a model to different stakeholders. See example at the end of this section.

A click on the icon Packages opens the packages menu on the right side. Packaging allows you to create a custom folder structure, include / exclude objects of a model and save the selection in an .xlsx or .json file. Options that cannot be used in the current situation are greyed out.
Select all elements contained in the package.
Show package elements. This doesn’t affect other elements.
Hide package elements. This doesn’t affect other elements.
Create new package in the selected level / folder. If nothing is selected it will be created on the top level.
Create new folder in the selected level / folder. If nothing is selected it will be created on the top level.
Delete selected package / folder.
Duplicate selected package.
Save all folders / packages.
Load a folder / package.

Creating / loading folders / packages

Load or create a new folder / package by clicking on the respective icons. After that, you have access to the Definition area in which you can add definitions and connect them by using logical operators.
If there already is a folder / package prior to loading another one, you can either replace the existing folders / packages or append them.

If you try to load a package that doesn’t contain any conditions loading will abort with an error message. If you accidentally saved a folder that contains empty packages simply open the .xlsx or .json file and delete any empty package

Deleting / saving folders / packages

Delete a folder / package by selecting it and then clicking on the icon Delete. You will be asked if you really want to delete the folder with all its content.
Clicking on the save icon will always save the whole folder structure regardless what you have selected. A message will appear if there are any empty definition groups.

Organising folders / packages

You can drag folders / packages to the end of the list and into / out of folders.

Visualisation

After selecting a package you can show its elements only or grey out the rest.

Defining packages

Start by loading or creating a new package. After that you have access to the “Definition” area. There, you can add definitions and connect them with logical operators (AND NOT, OR, AND).

Condition by attribute Condition by volume
Options -Equal -Inside
-Not equal -Overlap
-Like (wildcards) -Outside overlap
-Not like (wildcards) -Outside

After selecting a package you have access to the tools for condition definition:

Condition by volume

You can choose which area defined by the volume you want to include by clicking on the downward arrow of the selected condition:

Inside / outside

Define a volume like you would do with volume clipping. All objects that are completely inside outside this volume are part of the package.

Inside / outside overlap

Define a volume like you would do with volume clipping. All objects that are / aren’t at least partly inside this volume are part of the package.

Condition by attribute

You can choose an attribute (approval status, area …) expressed by a character / number string to define objects you want to include and a matching condition:

Equal / not equal

The attribute exactly matches the string entered in the text box.

Example: Uid = c0fc06552004 for exactly this object with exactly this unique ID.

Like / not like

The attribute exactly matches the string with wildcards entered in the text box.

? for exactly one character.

* for any number of characters.

Example: Uid c0fc06552? for all objects with the unique ID c0fc065520c0fc065529 and c0fc06552ac0fc06552z including all valid characters.

Using wildcards: If you use equal / not equal the characters ? and * stand for ? and *. If you use like / not like instead, ? and * can stand for any (number of) character(s). You can only add wildcards to the start or end of search strings.

Grouping conditions

It is possible to group conditions and nest them inside one another.

With an IntelliGroup you have to choose a radius. All objects that are at least partly inside that radius, are included in the package. A radius of 0 means the objects are touching an object in that group.

Example

Your model contains an area that’s classified for security reasons. You want contractors to have access to your model and exclude the classified area. In this case you can include the classified area in a package. You can do this by defining rules combining attributes and / or volumes.
If you want to exclude the selected parts of your model, you can do this by the following steps:
Create a new package.
Select all objects you want to exclude. In the definition area click on Condition by volume.

Choose Inside

A click on the highlight icon reveals that the selected volume also contains some small pipes and structural parts that shouldn’t be part of the package:
To exclude the structural parts create a new condition. This time choose Condition by attribute.

As the FileName attribute of all objects to exclude contains Structure select FileName in Available attributes and enter Structure in the text box. In this case you can use exact (“Structure”) or fuzzy matches.

Now choose and not as the logical connective, so that all objects included in the first condition are inside the selection except from the objects that are defined in the second condition.

To exclude the two nozzles select them and create a Condition by volume with Inside as an attribute.

Connect that condition with “and not”:

Your package now only contains the desired objects:

This is only one of many possible ways to get this result.

The last step is to save your package by clicking on the icon “Save package”. Enter a name and choose a file format.

In UniversalPlantViewer Builder you can load this as packages definition file.