A

Add comparison Workspace A chart option that creates comparisons across a selected dimension (for example, years or scenarios) for the selected visualization.

Aggregation Model Summarizing data across levels (for example, Month → Year). The levels used determine how values are combined, and the behavior can be controlled per node.

Aggregation settings Model Node settings that define how aggregation behaves for display and for calculation. Display aggregation affects workspace visuals, while calculation aggregation affects model results.

Alignment Model How values from different inputs are matched before a calculation is applied. Alignment is primarily driven by shared dimensions and levels.

Allow simulation Model A node setting that makes a node selectable for simulation changes. Only nodes with simulation allowed can be modified by assumptions and measures.

Annotation Model Contextual information attached to model elements to explain assumptions, decisions, or changes. Annotations improve interpretability without affecting results.

Assumption Scenario Manager A bundled set of simulation changes that represent a presumption or view about the future. An assumption typically groups multiple line-items for a financial concept.

Assumption group Scenario Manager A higher-level category used to organize line-items. It bundles multiple line-items under one assumption.

Assumption Line-Item Scenario Manager A single change to the base data that affects exactly one node and is always non-destructive. Line-items are used to apply controlled adjustments while preserving original data.

Assumption properties Project Custom attributes defined per assumption to structure and filter assumptions. Properties are set up by administrators and use predefined value lists.

B

Base Scenario Manager A line-item column that shows the node values from the underlying model scenario. Base values are read-only and represent the unmodified starting point.

Baseline Model The model scenario used as the reference point for simulations and comparisons. It is the basis of all simulation scenarios and is not impacted by simulations.

Baseline/Base Scenario/Default Scenario Workspace A special scenario that serves as the foundation for all simulations and remains unchanged by assumptions. It provides the stable reference for all scenario results.

Bottom-Up Modeling Model A modeling approach where values are defined at a detailed level and aggregated upward. This supports traceability from drivers to totals.

Business Key Project A unique identifier for a project across the entire instance. Unlike the project name, it must be globally unique.

C

Calculated Node Model A node type that is computed from other nodes using operations and functions. It represents derived logic rather than direct input data.

Calendar months Project An optional dimension (“CalendarMonth”) with values 01–12 used to analyze seasonal effects across years. It differs from Month because it does not include the year.

Change Scenario Manager A line-item column where simulation changes are entered and saved. The result is computed as Base + (Further effects, if present) + Change.

Chart Workspace/Worksheets A graphical representation of model or simulation values. Chart types determine how series are displayed for analysis and comparison.

Chart filter Workspace A filter applied only to a single chart. It restricts chart content without changing other workspace objects.

Compound Unit Model/Workspace A unit that relates two units to each other (for example, Quantity / Euro). It is commonly used for ratios such as prices.

Configure axes Workspace Inspector functionality that defines what is shown on chart axes and in series. It controls which dimensionality is displayed in the visualization.

Configure hierarchy Dimension Management A function to create new levels and adjust the ordering of levels within a dimension. It defines the hierarchical structure used across the project.

Configure submodels Model A configuration that links models into a structured system of submodels. It enables a driver structure and shared access to lower-level model data.

Connector Color Model A setting that defines the color of the connector lines between connected nodes. It helps visually distinguish relationships in the model.

Consistency Model The property that results follow the same logic across all relevant dimensions and scenarios. Consistency is achieved through structured modeling rather than manual replication.

Cross effects Workspace An interaction effect that occurs when multiple drivers change simultaneously and the combined impact is not simply additive. Cross effects are commonly shown in bridge charts.

Cube Model The multi-dimensional data structure that every node holds. A cube is defined by its dimensions and levels; each value exists at a specific intersection across all included dimensions. Cube size is the total number of intersections and grows with the cross product of level members. See Cubes.

D

Data node (absolute) Model A node type representing data input values interpreted as absolute values. It is used to bring data into the model context.

Data node (relative) Model A node type representing data input values interpreted as relative changes. It is used for rate-based or delta-like inputs.

Data preview Model A preview of the values for the selected node in the model. It is used for quick validation and understanding of what data arrives.

Data Source Overarching/Model A source of uploaded or connected data used as input for modeling. It can be an uploaded file, manually entered tables, or an external database connection.

Default Scale Model A node setting that defines a default scale used when visualizing the node in charts (for example, always show in millions). It standardizes chart readability.

Default scenario Workspace The chosen baseline that new simulation scenarios are based on in a workspace. It defines the baseline context for simulation changes.

Dimension Dimension Management/Model/Workspace A core structural category such as Time, Location, or Product that organizes values. Dimensions contain one or more levels and define how data is sliced.

Dimension hierarchy Dimension Management The ordering of levels within a dimension from less detailed to more detailed. It defines how roll-ups and drill-downs are structurally interpreted.

Dimension management Dimension Management The area where dimensions, levels, and level values are created and maintained. It acts as central master data management for structure.

Driver Model A variable input that influences dependent values through model logic. Drivers make cause-effect relationships explicit.

Driver tree Model A representation of a business model as cause-effect relationships between key figures. It maps interdependencies to explain how results are derived.

E

Expansion Model Creating values at a more detailed level from less detailed inputs. Expansion increases granularity while preserving structural rules.

F

Formula Model A calculation expression used to define cause-effect relationships between nodes. Formulas can include arithmetic operations and named functions and are written in the operation field.

G

Global Workspace Filter Workspace A workspace-wide filter that restricts what data can be viewed or changed across all worksheets and charts. It applies consistently to all workspace tabs.

Group Key Model A setting that groups how effects are displayed in bridge charts. It allows multiple nodes to share the same grouping label in effect displays.

GroupRemovedParametersSeparately Project A project setting that controls whether removed assumption or property groups appear separately in assumption bridges. It affects how additions/removals are represented.

H

Hide in workspace Model A node setting that removes the node from workspace selection and visualization. Hidden nodes remain part of model logic but are not exposed in workspaces.

Hide outgoing connectors Model A node setting that hides connector lines leaving the node. It reduces visual clutter in complex model structures.

Horizon level Project The time level that determines how horizon start and end are specified (for example, year vs. month). It does not limit the temporal detail available in modeling.

I

Impact Proxy Model A model setting used to represent or proxy impacts for analysis. It supports clearer effect attribution where direct representation is not desirable.

Imported scenarios Project Fixed scenario values imported from external sources for comparison in charts. Imported scenarios cannot be changed and are used as reference benchmarks.

Include in export Model A node setting that controls whether a node can be selected for scenario export. Nodes are exportable by default unless excluded.

Inspector Workspace/Worksheets A context-sensitive panel used to configure selected objects, especially charts. It is located on the right.

Instance Overarching The technical environment where Valsight is installed and operated. Instance settings define the boundary for projects and administration.

L

Level Dimension Management/Model/Workspace A layer within a dimension hierarchy that defines a degree of detail (for example, Year, Quarter, Month). Levels structure how aggregation and analysis behave.

Level value Dimension Management/Model/Workspace A specific member of a level that “fills” the level with concrete values (for example, 2022, 2023). Level values define the selectable members for analysis and data.

Line-item Scenario Manager The smallest element of a simulation that changes exactly one node’s data. A line-item is always assigned to an assumption and changes simulation-enabled nodes only.

Linked Levels Dimension Management/Model/Workspace Level values that are linked to values in another dimension. Linked levels support cross-dimensional mappings and consistent structural relationships.

M

Measure Scenario Manager A bundled set of consequences or actions that have an effect on a determined area. Measures represent planned interventions (for example, hiring, investing) rather than observations.

Model Model A structured representation of relationships and calculations for a business or business area. A model contains nodes, can be split into submodels, and defines cause-effect logic.

Model editor Model The view where model logic and calculations are defined using nodes and their connections. It represents the model visually and structurally.

Model graph Model A visual overview of models and their connections within a project. It supports understanding and navigating complex submodel structures.

Model horizon Model The time period applied in a model, defined by horizon start and end. It can differ from the project horizon, though it matches by default.

Model name Model A unique name for a model within a project. It is commonly structured with numeric prefixes to support sorting and clarity.

Model scenario/Baseline Model/Workspace A default data view in the model that serves as the basis for simulations. Models can contain multiple baselines to support scenario-specific logic.

Model validation Model A model check that validates node calculations and formulas for correctness. It surfaces syntax or logic errors across the model and its submodels.

N

Node Model The smallest element of a model used to represent a key figure and its calculation logic. Nodes define cause-effect relationships through operations and can be of different types.

Node editor Model The configuration area for a selected node where properties like name, unit, and settings are adjusted. It controls how the node behaves and is presented.

Node ID Model A technical identifier that uniquely identifies a node in the system. It is used internally to reference the node reliably.

O

Open Workflow A workflow status indicating that a step is available to be started. It represents the initial state before execution begins.

Operation Editor Model The field used to enter formulas and calculations for a node. It supports comments using a hash sign (#) that do not affect logic.

Operation per scenario Model A capability to define different logic per model scenario within the same node. It allows scenario-specific calculation behavior inside one model structure.

P

Presentation Workspace A saved version of a workspace visualization that can be shared for viewing without project permissions. Presentations can include selected worksheets and support exporting to PDF.

Project Overarching A container that bundles models, data, dimensions, simulations, and visual outputs for a specific use case. It represents the organizational unit for planning work.

Project horizon Overarching The time period applied to the project, defined by horizon start and end. It sets the default temporal scope across project elements.

R

Reconfigure Scenario Manager A line-item action used to update or re-edit configuration such as filters or input mode. It is commonly used to resolve errors or refresh settings.

Result Scenario Manager A line-item column that displays the computed simulation result (Base + Further effects + Change). Values entered here are not saved directly; only the implied change is saved.

S

Scenario Workspace/Scenario Manager A representation of a possible future defined by a set of assumptions and measures. Scenarios are used to compare alternative developments.

Scenario assumption Workspace/Scenario Manager A saved, uneditable bundle of active assumptions from a shared scenario. It enables sharing scenario logic across workspaces consistently.

Scenario bridge Workspace A chart that explains differences between scenarios at a point in time by attributing impacts to assumptions and effects. It supports transparent scenario comparison.

Scenario export Workspace/Scenario Manager An export of scenario results for selected nodes (for example, to Excel, CSV, or OData). It enables downstream reporting or integration with other systems.

Scenario Management Workspace Managing the shared scenarios within a project, including visibility and access. It provides an overview of scenarios shared by you or other users.

Scenario Manager Workspace/Scenario Manager The workspace area where scenarios, assumptions, and measures are defined and managed. It acts as the simulation cockpit for planning and analysis.

Scenario selection Scenario Manager A line-item option that displays effects from other active simulations in the selected scenario. It introduces the “Further effects” component in the base-change-result logic.

Section/Divider Model A visual divider used to separate and organize nodes in the model editor. Sections support readability without affecting calculations.

Share Scenario Manager – Scenario A scenario action that bundles active assumptions into a shared, fixed scenario assumption. Shared scenarios can be reused across workspaces and users.

Shift Scenario Manager A feature that moves assumptions in time to earlier or later periods. It supports timeline adjustments without rebuilding line-items.

Show data effects in bridges Model A setting that controls how data-driven changes appear in bridge visualizations. Effects can be shown as generic “Data” or attributed to specific nodes or group keys.

Simulation Workspace/Scenario Manager Calculating alternative outcomes by applying assumptions and measures on top of a baseline while using the same model logic. Simulations are non-destructive and dimension-consistent.

Simulation horizon Workspace The time period applied within a workspace simulation, defined by horizon start and end. It can differ from the project horizon, though it matches by default.

Simulation scenario Scenario Manager A scenario created in the Scenario Manager that combines a selected model scenario with active assumptions and measures. It represents a specific simulated future state.

Simulation UI Overarching The user-facing part of Valsight used for modeling, simulation, dimension management, and analysis. It is distinct from administrative configuration areas.

Simulation Workspace Workspace A sandbox environment built on a model to create simulation scenarios and analyze results. It supports comparing outcomes using charts and tables.

Single Select Model A node selection mode where each node is selected individually. It is used when precise single-node selection is required.

Sort and Format Workspace Inspector options to adjust ordering, formatting, and styling for selected chart contents. It applies after content selection is defined (for example, via Configure axes).

Standard node (no simulation) Model A node configuration that is not intended to be modified in simulations. It remains model-only and serves as structural or calculated logic.

Standard node (simulation) Model A node configuration intended to be changed through simulations. It is selectable in the Scenario Manager when simulation is allowed.

Submodels Model Linked models that form a larger model structure with shared access to lower-level nodes and data. Submodels support clean decomposition of complex organizations and driver structures.

Save as template Workspace/Scenario Manager A function that saves assumptions for reuse, including selected line-items and filters. It supports repeatable scenario setup.

T

Template Manager Template Manager A feature that manages templates used for exporting scenarios. It defines which nodes are included in an export and how exports are structured.

Templates Template Manager/Workspace Blueprints used to export scenario results for selected nodes. Templates standardize scenario exports across users and cycles.

Tree diagram Workspace A visualization of model logic starting from a selected root node. It helps analyze and trace how a final key figure is derived.

Tree Select Model A node selection mode that selects a node and all nodes downstream of it. It supports bulk selection of connected logic paths.

U

Unit Model/Workspace A display setting that defines how a node’s key figure is expressed (for example, EUR, units). Units standardize interpretation and visualization.

Upload Data Model A function that updates or uploads data sources directly from the model editor. It supports refreshing existing data sources used by the model.

V

Validation node Model A specifically configured node used to validate model correctness. A validation result of 0 indicates valid logic, while non-zero indicates an issue.

Validation Node Checkup Model A manual process to run validation nodes and verify model correctness. It must be executed actively and does not run automatically in the background.

Variant Workspace/Scenario Manager A grouped variation of a single line-item used to test alternative changes under the same conceptual change. Variants improve Scenario Manager clarity and scenario usability.

Variable Model/Workspace/Scenario Manager A project-wide quantity referenced in modeling and simulation, always starting with a $ sign. Variables can be numeric or non-numeric and support reusable logic.

Version Overarching The installed software release level of a Valsight instance. Versions introduce technical improvements and new features and can be checked in the application footer.

Versioning Scenario Manager A concept for managing changes over time and tracking revisions in scenario configuration. It supports stable planning cycles and controlled evolution of assumptions.

View Scenario Manager A line-item option that controls scaling, decimals, and visible columns for that line-item. It adjusts presentation without changing underlying logic.

W

Workflow Workflow A feature that structures and supports a multi-user planning process through defined steps. It standardizes execution and provides process visibility.

Workflow run Workflow An instance of executing a workflow across its steps. It represents an active planning cycle using the defined workflow structure.

Workspace Workspace A simulation environment based on an underlying model where scenarios are created, analyzed, and compared. Workspaces combine Scenario Manager changes with visualizations on worksheets.

Workspace filter Workspace/Scenario Manager A global filter applied across the entire workspace, affecting worksheets, charts, scenarios, and assumptions. It can be used to restrict scope or responsibility.

Workspace validation Workspace A validation process that checks for technical, logical, and user-defined errors in a workspace. It supports reliable simulation execution and interpretation.

Worksheet Workspace A canvas for creating and arranging charts and other visualizations. Worksheets structure analysis into tabs and can be selectively included in presentations.

Y

YoY-bridge Workspace A year-over-year bridge chart comparing points in time within a scenario. It attributes changes over time to effects and assumptions for transparent analysis.