For the list of all supported Decision Insight downloads and releases, see the Downloads page.


A model is the data model of your monitored process in Decision Insight. The model is the central component that describes what information is available to the application and includes the description of entities, their attributes and how they relate to each other. These relationships are the glue that binds an application together.The data model sits at a balancing point between technical and functional skills. Some tasks of model definition can be quite technical. The scope and direction of the model require business-aligned functional thinking.

The process of designing and configuring a data model starts with a clear understanding of the business process from a functional point of view. Misunderstandings about the business, how it works, how individuals view and interact with it are the most frequent root causes of implementations that will require rework before acceptance.


The model is not necessarily a model of the business process itself. In Decision Insight, the representation of entities and their relationships depends more on the scope needed to meet the needs of the observer and the reality of the visibility into the available data. Decision Insight models can grow and extend as the use and understanding of the solution increases.

Know the scope of what you must deliver in order to provide value from the solution. When you are only monitoring a subsection of the process, it is an unnecessary effort and expense to define a model of the entire business process.

The first, easiest and most expensive mistake an analyst can make when creating a model is to try to include everything. Beware of bloat.

Related Links