Skip to content

Global and Local Values

Save Time With Global Values

If a component occurs simultaneously in several variants of a project, you need to change a value in only one component with the default global setting in order to effect this change in all components of the same name in the project.

This makes parameterization easier and saves time.

Global values with the same identifier are the same in the components of the same name in all variants throughout the project.

However, to deviate from this principle and set values in components with the same name individually for each variant, you can Switch the values to local and only change them in one variant.

The values of the components can be global or local.

Example (see figure above)

The Heat_Demand component occurs in the two variants Reference case and Var1-CHP. The Minimum heat demand is a local value and the Maximum heat demand is a global value.

If the Minimum heat demand in the component Heat_Demand is changed in the Reference case this only affects this component.

If the Maximum heat demand in the component Heat_Demand is changed in the Reference case this change of the value is also automatically effective in the component Heat_Demand in the variant Var1-CHP.

If you change a local value, it will be changed only in the component you are currently editing. If a component with the same name also occurs in other variants, the corresponding value with the same identifier is not changed in these other variants.

Distinguishing Global and Local Values

You recognize global values by the identifiers being printed in bold and the menu button at the end of the line not having a grey location symbol (inverted drop) on the blue stripes at the top left as with local values (see following figure). You will also see the Switch to local entry in the context menu of the identifier or the pop-up menu of the parameter.

You recognize local values by the blue menu button at the end of the line also bearing the grey symbol for the location: . The identifiers of local values are not displayed in bold. In their context menu, you will find the entry Switch to global (see following figure).

In short, you can recognize global values by the bold print and local values by the local symbol (see following figure).

Changing Global Values

Changes to global values affect all components with the same name (all representatives/instances of a component). The concept of instances of a global component that are used at different points in a project is described in the article about the Components. If a global value is changed, the value is changed in the components of the same name in all variants. Changing and adding a time series that belongs to a global input value affects all instances of the component in all variants. If a component has further instances in the project and a global value of this component is changed, a time series is added to it, or the corresponding time series is opened in the ETA, a message dialog appears (see following figure). This lists all components and their values that are changed by the input.

The dialog can be deactivated via the Don’t show dialog anymore option. The global values are then immediately changed globally without prompting. To reactivate the dialog later, select Confirm changing of global form data in the Options dialog under General → Saving options.
Global values can be linked with master data.
Global values of a component become local when data are transferred from the Component database. You can then Switch them back to global.

Switch Between Global and Local

To change a global value to a local value (or vice versa), right-click on the identifier of the value and select  Switch to global or  Switch to local in the context menu that opens (see figures above). When switching to global, the following dialog appears, which lists the other affected components and values in the project (see following figure).

If you confirm the change with OK, the current value of the component is transferred to all other instances of the component that occur in other variants. You can enable and disable the display of this dialog in the Options dialog under General → Saving options → Confirm adoption of global form data.

Default Setting for Input Values

The default setting for Input data is global.

Updates of older projects are an exception. In projects from TOP-Energy versions prior to 3.3.0, all values are set to local during the update. You recognize this by the menu button with the location symbol for local values (see above).

In older projects, the number of component parts may not be the same. Therefore, after the update, you can Switch the component parts below a heading from local to global once using the additional function of the menu button behind the heading (see following figure).

The Transfer component parts dialog then appears, and the components are then in the state of the current version.

Adding and Removing Component Parts

Adding and removing of component parts is always global so that all instances of a component contain the same component parts. This also applies to the deletion of components that were previously local. Set components that are not required to local and assign them the value 0 afterwards.

Calculated Values

The calculated values of a component differ from variant to variant. They are displayed in blue. By default, calculated values (usually output data) are always local data.

The methods described above can also be used for Output data. However, this is only recommended for experts. For this reason, this function is secured by a editlock_s lock in the Home ribbon which must be opened before the output data can be edited.

Video

The video shows how global and local values work, still using an older TOP-Energy version.

Back To Top