A model provides a grammar for describing the aspects of an application that are key for tracking business performance and mapping those concepts to existing software application implementation. In general, models of a high-level application are defined through an iterative collaboration between a business user and an architect. The business user generally describes the high-level concepts associated with an integration application, whereas the architect refines those concepts and maps them to an application implementation. Once the model is defined and mapped, the system starts collecting metrics associated with instances of the business model. The metrics are used to render dashboards and reports.
Creating a model involves collaboration between users that have different personas: business users and architects. Business users define the abstract model, including milestones and indicators, while architects map those abstractions to underlying artifacts such as services and components.
A model includes:
Basic metadata
Identifier — this is the unique identifier which identifies an instance of the model and it is mandatory to define it
Set of ordered milestones and their associated indicators.
For detailed description about milestones, indicators, and identifiers, see Understanding Oracle Real-Time Integration Business Insight.