This Decision Insight glossary provides for various types of concepts. For some terms, click the available links to get more detailed information. 

Architecture concepts

Term Definition
Deployment A complete installation of Decision Insight (DI) where DI is up and running. For more information, see Deployment architectures.
Standalone installation Installation of the deployment as a single instance of DI deployed on a single node. For more information, see Standalone deployment.
Clustered installation Installation of the deployment as one cluster or a set of clusters. Clusters may have a functional role or a technical role or both. For more information, see Clustered deployment.
Cluster ID The cluster ID uniquely identifies clusters within your deployment. All nodes within a cluster should have the same cluster ID. A cluster ID a 64-bit identifier that is represented with 3 groups of hex digits for human readability (for example, xxxxxxxx-xxxx-xxxx where x are hexadecimal digits).

Time concepts

Term Definition
Observation mode The way you observe data on your dashboard using the time machine. you can observe data at a given instant or see how it evolves over an interval of time.
Rhythm A rhythm is an increment of time used to define the granularity of time within an application and within components of the application.
Transaction time (TT) The time when the deployment is aware of a given piece of data. This is used mostly for monitoring and past data management.
Valid time (VT) The time related to a piece of data, that is the basic monitoring time axis.

Application concepts

Term Definition
Application The top-level structure in your deployment. Applications are used to organize your data. An application comprises a set of dashboards, along with the underlying model, computed attributes, and data integration elements.
Space Spaces act like containers to hold definitions that describe your solution.

Design concepts

Term Definition
Attribute An attribute is an element that holds a value of a supported DataType.
Baseline An initial collection of data on a given period and used as a basis for data comparison.

Entities are the key element of the meta-model. An entity centralizes a set of elements and is similar to a class  in an object-oriented language.

Instance Each object in a given entity is called an instance.

A calendar is an advanced feature that enables you to define attributes whose value changes according to configured rules.

Model The model is the data model of the monitored process in the deployment. The data model is the central component that describes what information is available for the application.

Data integration concepts

Term Definition

Mappings enable you to map data to Entities and Attributes .

Route Routes describe the path between the customer data and the model, entities, and attributes defined in the deployment.

Related Links