Celonis Product Documentation

A characteristic of an object or event. For example, an invoice has an ID, a total price, and a currency. The values of an object or event’s attributes show the current known facts about it. For example, if an invoice is for $50, the value of the total price attribute is 50.00, and the value of the currency attribute is US dollars.

A recorded alteration (insert, delete, or change) to a value of one attribute of an object - for example, inserting a value for the InspectionStartTime attribute of the QualityInspection object to record when the inspection started. The record of a change includes the timestamp for when the change took place, and the old and new values of the attribute.

Changes are optional but are often used to create events. They can only be captured if they are stored in your business data.

A digital representation of a real-world occurrence that happened, at a single moment in time, to one or more objects connected to your business. For example, a customer paying an invoice, a user creating a purchase order for a vendor's product, or a warehouse shipping an order, are all individual events.

Every event involves one or more objects, and can be identified from the data held in those objects and their changes. For example, the event of shipping an order involves both the warehouse the order shipped from, and the order that was shipped. An event type is a definition of what attributes and relationships an event has.

A definition of the relationship of one event to one object in a business process. An event can have multiple event to object relationships with different objects. For example, when a customer places an order, the event of placing the order relates to the order, and also and to the customer.

A definition of an event that happens to one or more objects during a business process (such as shipping an order), what attributes it has, and its relationships to objects.

An event type (for example, BeginQualityInspection) is a definition of what an event looks like. An event is a single instance of that event type (for example, employee Jules begins the quality inspection of a test kit from a purchase order at 2pm on August 25).

A collection of events connected to  a single object that’s built from the object-centric representation of a case. Event logs are created in a perspective to follow the events that happen to a single object during a process. They are compatible with apps and views that require case-centric representations. You can create many different event logs from the same perspective that is already populated with your data, and you can have multiple different event logs associated with a single lead object type.

An extraction is a task that identifies and ingests relevant business data from the tables in your source system into the Celonis cloud.

A digital representation of something connected to your business that exists in the real world. For example, a customer, a company, an order, or an invoice.  An object type is a definition of what attributes and relationships an object has.

A definition of the relationship of one object to another object in a business process. For example, an invoice and a customer are related to each other.

A definition of an object in a business (such as an invoice), what attributes it has (such as a currency), and its relationships to other objects.

An object type (for example, PurchaseOrderItem) is a definition of what an object looks like. An object is a single instance of that object type (for example, a test kit that is part of a specific purchase order).

The object-centric data model consists of object types and event types, related and arranged to model what happens in business processes.

Celonis supplies a set of object types and event types for objects and events involved in common business processes. You can extend the object-centric data model by adding custom attributes and custom relationships to the Celonis object types, and creating custom object types and custom event types to model processes specific to your business.

Object-centric process mining is an innovative method for visualizing and analyzing complex business operations. It involves representing the business as objects, events, and their relationships to explore the interconnectedness of business - how each object relates to others and is involved in multiple processes.

With an object-centric approach you can maintain a single model and a single set of data, and reuse your built objects and events to analyze multiple processes. You can also easily assemble objects, events, and their relationships into event logs to support case-centric applications.

A set of object types, event types, and relationships to represent a particular business process or grouping for analysis. Perspectives pick out a subset of the object-centric data model containing the relevant relationships for the process you want to analyze, to create an unambiguous query context. Perspectives can be used for the same purposes in object-centric process mining that Data Models are in case-centric process mining.

For object-centric process mining, a transformation is an SQL query that creates objects or events. A first group of transformations creates objects and changes based on business data ingested by extractions. A second group of transformations creates events based on those objects and changes.